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/leifericf/agentic-sdk/add-dimensionnpx skills add leifericf/agentic-sdk --skill add-dimensiongit clone --depth 1 https://github.com/leifericf/agentic-sdkWrote 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/leifericf/agentic-sdk/add-dimension)<a href="https://agentmods.dev/skills/leifericf/agentic-sdk/add-dimension"><img src="https://agentmods.dev/badge/skills/leifericf/agentic-sdk/add-dimension.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.00020 | $0.00874 |
| Opus 5 | $0.00010 | $0.00437 |
| Sonnet 5 | $0.00004 | $0.00175 |
| Haiku 4.5 | $0.00002 | $0.00087 |
Grade A, and why
add-dimension 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 4d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
add-dimension
Role: the dimension meta-skill. Generate a draft check- recipe from the dimension shape for a bug class the active dimensions miss, and wire it into the descriptor.
Prerequisites
~/.agentic-sdk/<project>/project.edn exists (run bootstrap-project first). A real bug
class the active :dimensions-active set missed, the way a
memory-unsafe language needs check-memory. The bug class is general,
not a one-off.
Procedure
Follow the shared add-* procedure in docs/design.md section 8.3:
detect the gap, interview for the skeleton's variable slot, generate
against the skeleton, wire into the descriptor, validate.
- Detect the gap. Confirm the bug class is not already covered by
an active dimension. The catalog in
docs/design.mdsection 11 is the reference: check-correctness, check-factoring, check-style, check-conformance, check-security, check-performance, check-portability, check-memory, check-design (UI only), check-clarity. A one-off bug is a fix-bug item, not a dimension. - Interview for the shape. Ask one batch of at most three questions
for what the dimension shape needs: the one-sentence failure model
(what goes wrong), the ordered look-fors (where to look, in priority
order), the ignore-rules (what not to flag), the default severity
(
:high,:medium, or:low), and the level (:correctness,:factoring, or:style). Acheck-<dimension>sets:levelto one of those three keywords;triageorders correctness, then factoring, then style, then lint. - Generate the recipe. Author
skills/check-<dimension>/SKILL.mdfrom the dimension shape: frontmatter (name: check-<dimension>, model-invoked, read-only reviewer), the one-sentence failure model, the ordered look-fors, the ignore-rules, the severity, the level, and the return contract (NO FINDINGSor the EDN finding shape fromskills/shared/references/review-model.md). The reviewer agent loads this recipe per shard. - Wire the descriptor. Add the dimension keyword to
:dimensions-active. If the dimension requires a condition (the way check-design requires:ui? true, or check-memory requires a memory-unsafe language), state the condition in the recipe and confirm the descriptor satisfies it. - Validate. Run one review round using the new dimension: a reviewer runs it over a shard that exhibits the bug class. The dimension earns its place when it catches the class the active set missed and does not flood the punch list with false positives. Tune the look-fors and ignore-rules from what the validation surfaced.
- Land. One commit, category
Skills:.
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.
- 4d ago First seen · 77 lines · 20 tokens per session scan A dd9d933b4f42
add-dimension is a skill published in the GitHub repository leifericf/agentic-sdk (5 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 874 once invoked, about $0.0001 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…