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/assess-testingnpx skills add leifericf/agentic-sdk --skill assess-testinggit clone --depth 1 https://github.com/leifericf/agentic-sdkWhat 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.00011 | $0.00389 |
| Opus 5 | $0.00005 | $0.00195 |
| Sonnet 5 | $0.00002 | $0.00078 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
assess-testing 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.
What it actually says
assess-testing
Define the testing strategy (Tier 0/1/2). Declarative (what to test, not which framework); fast feedback first; right-sized, not maximal.
Procedure
- Read the dispatched inputs: the Gherkin spec, feature scope, and technical context (architecture, integrations, data flows).
- Tier 0 (required for all user-visible changes): unit tests for core logic, deterministic fakes or mocks for dependencies, contract tests at API boundaries; fast and isolated, seconds.
- Tier 1 (when applicable): required when the feature touches persistence, migrations, background jobs, or integration boundaries; containerized or local deterministic integration tests with real or test-container dependencies; minutes.
- Tier 2 (only when needed): required only when correctness depends on third-party behavior you cannot simulate; sandbox or external-dependency tests; allow retry and quarantine; on-demand before major releases.
- Define an E2E strategy only when the product has user-visible flows and a journey suite exists or is being introduced; focus on critical journeys.
- Set testing targets: local and CI loop under about five minutes; Tier 0 every commit; Tier 1 when integration-affecting chunks land; Tier 2 on-demand before releases.
Boundaries
Owns the test-tier strategy. assess-observability owns signals; plan-feature owns folding the result into the plan. Reached by plan-feature's fan-out.
Return
One EDN map: {:tier-0 {...} :tier-1 {:required ... :reason ...} :tier-2 {...} :e2e <str|nil> :goals {...}}.
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 · 41 lines · 11 tokens per session scan A 669507bcacb1
assess-testing is a skill published in the GitHub repository leifericf/agentic-sdk (5 stars, last pushed 14d ago), licensed MIT. It adds 11 tokens to every session and 389 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…