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 agentmods add skills/corridortech/posecap/ad-philosophynpx skills add CorridorTech/PoseCap --skill ad-philosophygit 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-philosophy)<a href="https://agentmods.dev/skills/corridortech/posecap/ad-philosophy"><img src="https://agentmods.dev/badge/skills/corridortech/posecap/ad-philosophy.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 | $0.00171 | $0.02713 |
| Opus 5 | $0.00086 | $0.01357 |
| Sonnet 5 | $0.00034 | $0.00543 |
| Haiku 4.5 | $0.00017 | $0.00271 |
Grade A, and why
ad-philosophy 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<background_information> Eight behaviors apply to every non-trivial change. Bias toward caution over speed; for trivial diffs, use judgment. A separate Documentation Discipline block applies to every document the agent writes. </background_information>
Think Before Coding. Don't assume. Don't hide confusion. Surface tradeoffs. State assumptions explicitly. Then apply Decide When Grounded (below) — if grounding resolves the uncertainty, decide; if it does not and the spec itself is fuzzy, route to /ad-grill-me instead of a raw open question. If multiple interpretations remain after grounding, present them — don't pick silently. If a simpler approach exists, say so. If something is unclear and grounding cannot resolve it, stop, name the confusion, and ask through /ad-grill-me for spec-level ambiguity or a single focused question with a recommended answer otherwise.
Ground Before Coding. Anchor in real patterns before writing code. For non-trivial changes, invoke /ad-ground — the workflow-operational skill that runs the four-source research pass (official docs, validated implementation references, in-repo patterns, git history) and synthesizes a happy path with citations. The skill carries the prescriptive deviation gate; this section carries posture only. Skip for diffs describable in one sentence.
Decide When Grounded, Ask When Judgment. Universal rule; WORKFLOW.md §7 subsection Decide when grounded, ask when judgment is the canonical source. The engineer is the boss, not the co-pilot. They are not reading every file the agent read to arrive at a recommendation. Default is decide, not ask. Take the grounded happy path from /ad-ground without asking. Pick the single-criterion winner from /ad-tdg without surveying. Take the well-established industry pattern without asking. State the deterministic outcome (gates green) as done. Ask only for: design/taste (UX, product tradeoff, brand-carrying naming), irreversible or high-blast-radius action (destructive git ops, force-push, deletion — match confirmation to blast radius not to diff size), genuinely close calls (two options tied on the picked criterion), insufficient evidence (a single unreproduced observation does not license autonomous follow-up creation — tasks, issues; mention it in the report, file only once it reproduces or the user explicitly asks), or fuzzy spec (route to /ad-grill-me, not a raw open question). Shape of the ask when warranted: one question, recommended answer first, why alternatives are weaker. Never a survey.
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.
- 3d ago First seen · 57 lines · 171 tokens per session scan A 5cb4be199338
ad-philosophy is a skill published in the GitHub repository CorridorTech/PoseCap (190 stars, last pushed 11d ago), licensed Apache-2.0. It adds 171 tokens to every session and 2,713 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…