Borrowing it
Nothing to install: this file belongs to CorridorTech/PoseCap. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/CorridorTech/PoseCap/main/.agents/skills/ad-bootstrap/SKILL.mdgit clone --depth 1 https://github.com/CorridorTech/PoseCapWrote 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/corridortech/posecap/ad-bootstrap)<a href="https://agentmods.dev/skills/corridortech/posecap/ad-bootstrap"><img src="https://agentmods.dev/badge/skills/corridortech/posecap/ad-bootstrap/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/corridortech/posecap/ad-bootstrap"><img src="https://agentmods.dev/badge/skills/corridortech/posecap/ad-bootstrap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 161 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00074 | $0.02261 |
| Opus 5.5 | $0.00030 | $0.00904 |
| Sonnet 5.5 | $0.00015 | $0.00452 |
| Haiku 4.5 | $0.00007 | $0.00226 |
Grade A, and why
ad-bootstrap 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<background_information>
Produces AGENTS.md at the repo root, ≤150 lines, every line operational. Generic agent behavior (think-before-coding, verify-before-claiming-done, etc.) does NOT belong here — that lives in the ad-philosophy skill.
Three modes, detected from filesystem state:
AGENTS.mdexists at the repo root → audit (do not rewrite, output drift list only)AGENTS.mdabsent and only trivial files present (.git,node_modules,.gitignore,.gitattributes,.DS_Store,.env*,.idea,.vscode,LICENSE*,README.md) → greenfield (interview by placeholder, no scan)AGENTS.mdabsent and meaningful code present → brownfield (scan first, pre-fill, ask only gaps) </background_information>
Step 1 — scan (brownfield only). Read in this order, taking the first that exists for each category:
- Manifests:
package.json,pyproject.toml,Cargo.toml,go.mod,Gemfile,composer.json,pubspec.yaml. README.md, plus anydoc/ordocs/directory.- Top-level directory listing.
doc/adr/— binding decisions; read every ADR.GUIDELINES.mdat repo root — if present, the AGENTS.md sections that have a corresponding GUIDELINES.md section (Code Style → §2; Quality Gates → §8; Commit & PR → §10; Security & Privacy → §12) emit as pointer stubs instead of inline rules' ' reciprocity and ADR-0030 §1..claude/,.cursor/,.openai/,.agents/— existing agent config.- Hook configs:
.husky/,.pre-commit-config.yaml,.github/workflows/,.gitlab-ci.yml,.circleci/. - Lockfiles:
package-lock.json,yarn.lock,pnpm-lock.yaml,poetry.lock,Cargo.lock. git remote -vfor the repo URL.
Build a model of: stack (languages and versions), entry points, build / test / lint commands, conventions, quality gates, security boundaries, gotchas confirmed by code.
Step 2 — pre-fill. For every <placeholder> in the template, fill from observed signals. No fabrication. If a section has no signal, write <TODO: not yet wired> in one line and move on. Do not write meta-prose explaining the gap.
Step 3 — show only the gaps. Print to the user:
- (a) placeholders that could not be filled from repo signals;
- (b) signals that conflict (two test commands, two style configs, README contradicts code, etc.).
One question per gap. Skip everything filled confidently. Do NOT ask philosophical questions ("is this doc for agents or humans?", "what is the most important quality bar?") — those are decisions, not interview material.
Step 4 — write the file. On user confirmation, write AGENTS.md at the repo root. Cut every line that does not change agent behavior. No "External Resources" section (URLs are derivable from git remote and the manifest). No appended Universal Agent Behavior block. No marketing prose.
Audit-mode override: do NOT write the file. Produce a drift list. Format each line as:
[file or section]: spec says X, code says Y. Suggested resolution: change spec / change code / discuss.
If something the user says contradicts what the code shows, surface the conflict. Don't silently trust the user; don't silently trust the code.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 191 lines · 74 tokens per session scan A 3c90471074dc
ad-bootstrap is a skill published in the GitHub repository CorridorTech/PoseCap (265 stars, last pushed 3d ago), licensed Apache-2.0. It adds 74 tokens to every session and 2,261 once invoked, about $0.0003 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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…