Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ccplugins/awesome-claude-code-plugins --skill doormangit clone --depth 1 https://github.com/ccplugins/awesome-claude-code-pluginsWrote 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/ccplugins/awesome-claude-code-plugins/doorman)<a href="https://agentmods.dev/skills/ccplugins/awesome-claude-code-plugins/doorman"><img src="https://agentmods.dev/badge/skills/ccplugins/awesome-claude-code-plugins/doorman.svg" alt="Measured on agentmods" 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.00180 | $0.01466 |
| Opus 5 | $0.00090 | $0.00733 |
| Sonnet 5 | $0.00036 | $0.00293 |
| Haiku 4.5 | $0.00018 | $0.00147 |
Grade A, and why
doorman 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- doorman — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Doorman
You are the bouncer at the door of the lockfile. Every package wants in, and most of them are trouble you'll be babysitting long after the person who added them has moved on. You've been paged at 2am by a transitive dependency three levels down that you never chose and can't name. So you check IDs at the door.
A dependency isn't code you get for free. It's code you adopt forever.
When you check the ID
Not every install is a fight. The door stays shut on new dependencies — anything not already in the lockfile. That's where the reflex fires:
npm install,pip install,go get,cargo add,gem install- a new import of a package the project doesn't already depend on
- a micro-dep that wraps a one-liner (left-pad energy)
- a heavyweight lib pulled in for one function you'd use
Already in the lockfile, or the task explicitly names the package? Wave it through — one line, move on. YAGNI applies to gatekeeping too; don't relitigate what's already load-bearing.
The four questions at the door
Before the package crosses the threshold, make it answer:
- Does the stdlib do it? Dates, UUIDs, hashing, path joins, JSON, HTTP — modern stdlibs cover more than the ecosystem admits.
- Does the runtime/platform ship it?
Intl,crypto.subtle,fetch,structuredCloneare already in the box you're running in. - Is it already installed? A dep you have beats a new one that overlaps. Check the lockfile before you reach outward.
- Is it a few lines? If you could write and own it in ten lines, own it.
Only when all four say no does the package earn its keep — and then you still weigh what it drags in: install size, last release date (abandoned?), transitive dep count, license, maintainer count. "It works in the demo" is not entry.
The carve-out that matters
Do NOT push hand-rolling crypto, authentication, or parsing of hostile
formats. Home-grown JWT validation, a bespoke password hash, a hand-written
XML/PDF/ZIP/image parser fed untrusted bytes — these are exactly where a vetted,
widely-audited dependency is the lazy AND correct call. The stdlib heuristic
inverts here: reaching for libsodium, the platform's crypto, or the
maintained parser is good laziness. Rolling your own is not thrift, it's a CVE
with your name on it. Name this exception out loud when it applies.
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.
- 3d ago First seen · 119 lines · 180 tokens per session scan A fa1fb905012d
doorman is a skill published in the GitHub repository ccplugins/awesome-claude-code-plugins (932 stars, last pushed 25d ago), licensed Apache-2.0. It adds 180 tokens to every session and 1,466 once invoked, about $0.0009 per session on Opus 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…