Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Brainrot-Creations/claude-pluginsnpx agentmods add skills/brainrot-creations/claude-plugins/get-domain-cookiesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/brainrot-creations/claude-plugins/get-domain-cookies)<a href="https://agentmods.dev/skills/brainrot-creations/claude-plugins/get-domain-cookies"><img src="https://agentmods.dev/badge/skills/brainrot-creations/claude-plugins/get-domain-cookies/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/brainrot-creations/claude-plugins/get-domain-cookies"><img src="https://agentmods.dev/badge/skills/brainrot-creations/claude-plugins/get-domain-cookies.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00027 | $0.00235 |
| Opus 5.5 | $0.00011 | $0.00094 |
| Sonnet 5.5 | $0.00005 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
get-domain-cookies scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Get Domain Cookies
Run the local helper script in this repo:
python3 plugins/amc-api/tools/getcookies.py <domain>
Behavior
- Return stdout exactly as the Cookie header string.
- If stdout is empty, report no cookies found for that domain.
- After retrieving cookie text, store it in AMC MCP using
amc_cookie_setsoamc_theatres,amc_showtimes, andamc_seatscan reuse it automatically. - If dependency is missing, instruct:
pip3 install --user --break-system-packages browser-cookie3
Example
python3 plugins/amc-api/tools/getcookies.py amctheatres.com
Then persist in plugin config:
amc_cookie_set(cookie="<paste-output-here>")
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 39 lines · 27 tokens per session scan A 517d206072bf
get-domain-cookies is a skill published in the GitHub repository Brainrot-Creations/claude-plugins (23 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 235 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
proof-e2e
Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".
e2e-panther-playwright
Write end-to-end tests with Symfony Panther 2.4 for browser automation or Playwright for complex scenarios.
octen-web-search
Use when anything needs live information from the web — looking something up, checking current or recent information, finding sources, comparing products / vendors / pricing, researching a topic, or reading a specific web page — even if the user never mentions Octen or the word "search". Also use before falling back…
playwright-qa
Driver P of orc:browser-qa — browser QA with Playwright Test and the stock planner/generator/healer agents against a resolved QA target; yields a stitched step-tagged video, traces, and qa-manifest.json.
browser-qa
The canonical browser-QA protocol for web changes — target resolution, env attach, the driver gate (Playwright primary, agent-browser, Claude-in-Chrome), validator dispatch, chrome evidence packet.
qa-targets
Resolve WHERE browser QA runs — named targets in .orc/targets.json (local, staging, preview), the Target gate, credential references (literal | op:// | env:), guard rule.