Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Cookie Compliance Planner — Map Consent & Tracking

    1

    Build evidence-linked tracker inventories, consent plans, withdrawal tests and governance actions.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Cookie Compliance Planner — Map Consent & Tracking

    Cookie Compliance Planner — Map Consent & Tracking

    Example session with this skill installed

    Illustrative scenario: Plan consent QA from these supplied observations for our website. Tracker A is an analytics tag observed firing before any choice and using local storage; purpose is audience measurement, but fields, recipient and duration are unknown. Tracker B is a session cookie supplied by engineering as maintaining login, with no measured trace provided. The preference panel has accept and reject options; withdrawal behavior is untested. We have users in Sweden and other countries but no confirmed regional configuration. Make an inventory, implementation plan and test cases. Do not browse, certify compliance or change production.

    • Read your context and instructions
    • Compiled the cookie compliance planner

    Tracking and consent planning brief

    Evidence consists of supplied observations and an engineering description. No independent scan, legal applicability determination or production test was performed. Regional requirements and legal classifications require qualified review.

    TechnologyEvidencePurposeActivation / storageMissing information
    A: analytics tagUser-supplied observationAudience measurement, suppliedFires before choice; local storage observedData fields, recipient, duration, consent dependency and backend uses
    B: login session cookieEngineering-supplied descriptionMaintain login, describedActual trigger and expiry not measuredTrace, cookie attributes, recipient, lifecycle and necessity assessment

    Issues and proposed implementation

    A: pre-choice firing is a factual discrepancy to investigate, not proof of a specific legal violation. Inventory the tag and downstream requests; obtain vendor configuration and data-flow evidence; map its execution to reviewed consent logic. B: validate the login purpose and lifecycle before categorizing it. Do not treat every cookie from this vendor as necessary.

    Document accepted, rejected, withdrawn and unknown consent states. Define category-level gates after legal/privacy review. Preserve the current CMP and tag versions, record proposed changes and prepare rollback. Synchronize notices and preferences with verified data, recipients and retention; do not invent notice text for unknown practices.

    QA plan — proposed, not run

    T1 Fresh visitor: clear test-state only in an authorized test environment; record pre-choice network/storage activity and consent defaults. T2 Reject: verify reviewed category gates, downstream requests and stored identifiers. T3 Accept: verify intended activation and consent evidence. T4 Withdraw: verify future execution stops where required and document existing identifier handling. T5 Return visit: verify stored preferences and version changes. T6 Regional/audience variants: test documented configurations, including authenticated and delayed behavior.

    For each test retain timestamp, property/environment, CMP/tag versions, region setup, consent state, observed requests/storage and deviations. Server-side uses need separate evidence.

    Owners and open decisions

    Engineering validates triggers and storage; marketing supplies tag/vendor purposes; privacy/legal reviews applicability, categories and disclosures; product approves preference behavior. These are proposed responsibilities, not confirmed assigned owners. Exact data, recipients, retention, mobile scope, regional rules and withdrawal behavior remain unresolved. No live settings or notices were changed.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Cookie Compliance Planner supports privacy, engineering, product and marketing teams in organizing verified website and app tracking behavior into an auditable implementation plan. It covers cookies, pixels, tags, SDKs, local storage, identifiers, session replay and server-side tracking where evidence exists.

    The workflow records purpose, data, recipients, duration, triggers and consent states; separates observed behavior from legal classification; identifies regional review questions; and plans preference logic, notices, QA, evidence and change governance. Supplied HAR files, cookie exports, tag-manager or CMP exports, source code, SDK inventories and screenshots can support the analysis when the host can read them.

    Outputs can include tracker inventories, discrepancies, pre-consent and post-withdrawal test plans, implementation tasks and review gaps. It does not classify a tracker as necessary from its name alone or certify legal compliance. Actual production changes and public notices require explicit authorization and review; a browser scan cannot reveal every backend use.

    Scans can miss conditional, authenticated, regional, delayed, server-side and dynamic tracking. Cookie or vendor names do not establish purpose or data flows. Behavior and laws change; jurisdiction-specific classification requires qualified review. No legal advice, certification or guarantee that a CMP meets every requirement.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Permissions

    Read Files
    Write Files

    File Scopes

    Authorized
    task
    inputs
    and
    agreed
    output
    directory
    only

    Read only authorized tracker inventories, code, HAR/cookie exports, CMP configurations and screenshots. Write reviewed plans to an agreed destination. Site inspection and connectors depend on permission and available tools. Production tags, CMP defaults, integrations, deletion and public notices require explicit authorization and rollback planning.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    No. It supports factual tracking analysis, consent architecture and issue spotting. Applicability, exemptions and jurisdiction-specific legal conclusions require qualified privacy/legal review.

    Provide authorized HAR traces, cookie/storage exports, tag-manager and CMP exports, source code or SDK lists, vendor inventories and test observations with timestamps and versions.

    No. Browser observations need to be supplemented for backend, server-side, conditional and regional behavior. It proposes tests and records missing evidence instead of claiming comprehensive coverage.

    New in Legal & Compliance