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/postindustria-tech/agentic-toolkit/reclassifynpx skills add postindustria-tech/agentic-toolkit --skill reclassifygit clone --depth 1 https://github.com/postindustria-tech/agentic-toolkitWhat 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.00087 | $0.00884 |
| Opus 5 | $0.00044 | $0.00442 |
| Sonnet 5 | $0.00017 | $0.00177 |
| Haiku 4.5 | $0.00009 | $0.00088 |
Grade A, and why
reclassify 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 2d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obligation Layer Reclassification
Reclassify obligation items from behavioral to schema where appropriate, shrinking the obligation coverage allowlist.
Context
Every obligation tagged **Layer** behavioral in obligation documentation requires an integration test (or allowlist entry). Many obligations are pure schema checks -- field presence, enum validation, serialization -- that can be tested with unit tests and mocked data. Reclassifying these as schema removes them from the behavioral obligation set.
Protocol
Step 1: Run deterministic classifier report
If your project has a reclassification script:
uv run python scripts/reclassify_obligations.py --report
Otherwise, manually review obligation documentation and apply the keyword scoring rubric below.
Review the output:
- Schema obligations (negative score): high-confidence reclassifications
- Behavioral obligations (positive score): correctly classified, no action needed
- Borderline obligations (score = 0): need LLM review in Step 2
Step 2: Review borderline obligations
For each borderline obligation (score = 0) that has both behavioral and schema signals, read the full scenario text and apply this rubric:
"Does testing this obligation require rows created/updated/deleted in a real database, external service calls, or multi-step state transitions? If yes -> behavioral. If it can be tested with mocked data and schema assertions alone -> schema."
For borderline obligations you decide to reclassify:
- Open the source doc file
- Find the
**Layer** behavioralline after the obligation's**Obligation ID**line - Change
behavioraltoschema
Step 3: Apply deterministic classifications
If you have a reclassification script:
uv run python scripts/reclassify_obligations.py --apply --regenerate-allowlist
Otherwise, manually update the allowlist to include only behavioral obligations.
Step 4: Verify guard passes
# Run your project's quality command
make quality
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.
- 2d ago First seen · 98 lines · 87 tokens per session scan A 48b9e29a007c
reclassify is a skill published in the GitHub repository postindustria-tech/agentic-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 87 tokens to every session and 884 once invoked, about $0.0004 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-31.
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…