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-datanpx skills add leifericf/agentic-sdk --skill assess-datagit 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/assess-data)<a href="https://agentmods.dev/skills/leifericf/agentic-sdk/assess-data"><img src="https://agentmods.dev/badge/skills/leifericf/agentic-sdk/assess-data.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.00013 | $0.00434 |
| Opus 5 | $0.00006 | $0.00217 |
| Sonnet 5 | $0.00003 | $0.00087 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
assess-data 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.
What it actually says
assess-data
Plan data migrations, backfills, and rollback strategy. Declarative and stack-agnostic; prefer reversible changes; flag fragile rollbacks.
Procedure
- Read the dispatched inputs: the Gherkin spec, feature scope, and technical context (data model, store type).
- Determine applicability. Required when the feature adds, modifies, or removes columns or tables, changes data formats, requires backfilling, or introduces new entities or relationships. N/A when purely visual, behavior-only logic with no data impact, or read-only over existing data.
- If Required, name the migration type (schema-only, backfill, expand/contract) and why. Define the up migration (DDL or DML, breaking changes). Define the down migration when safe; if fragile, say why.
- For expand/contract, give the three steps: expand (add without removing), deploy (write to both), contract (remove old after verification). For backfill, state online or offline, idempotency, restartability, and partial-rollback behavior.
- State rollback considerations: what happens if the migration fails or the deploy is reverted, and any consistency risks. Prefer separate deploys for schema migrations and data backfills; never combine a large rewrite with DDL in one migration.
Boundaries
Owns the data and migration strategy. assess-rollout owns deployment; plan-feature owns folding the result into the plan. Reached by plan-feature's fan-out.
Return
One EDN map: {:applicability :required|:n/a :n/a-reason <str> :migration-type ... :up ... :down ... :expand-contract <str|nil> :backfill <str|nil> :rollback ... :safety ...}. For N/A, only :applicability and
:n/a-reason.
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 · 44 lines · 13 tokens per session scan A 1849ef502e12
assess-data is a skill published in the GitHub repository leifericf/agentic-sdk (5 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 434 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…