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/pilotspace/pilot-space/adr-litenpx skills add pilotspace/pilot-space --skill adr-litegit clone --depth 1 https://github.com/pilotspace/pilot-spaceWrote 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/pilotspace/pilot-space/adr-lite)<a href="https://agentmods.dev/skills/pilotspace/pilot-space/adr-lite"><img src="https://agentmods.dev/badge/skills/pilotspace/pilot-space/adr-lite.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.00507 |
| Opus 5 | $0.00006 | $0.00253 |
| Sonnet 5 | $0.00003 | $0.00101 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
adr-lite 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.
What it actually says
ADR-Lite Skill
You are helping the user create a lightweight Architecture Decision Record (ADR) as a Decision Record PM block.
Steps
- Understand the decision: Parse the user's question to identify what needs to be decided.
- Research context: Use
search_notesto find related discussions or prior decisions in the workspace. - Generate options: Create 2-4 options with pros, cons, effort estimates, and risk levels.
- Insert Decision Record: Use
insert_blockto add a pmBlock with blockType='decision'.
Output Format
Insert a pmBlock with the following data structure:
{
"type": "pmBlock",
"attrs": {
"blockType": "decision",
"data": "{\"title\":\"[Decision Title]\",\"description\":\"[Context and problem statement]\",\"type\":\"multi-option\",\"status\":\"open\",\"options\":[{\"id\":\"opt-1\",\"label\":\"[Option A]\",\"description\":\"[Brief description]\",\"pros\":[\"Pro 1\",\"Pro 2\"],\"cons\":[\"Con 1\"],\"effort\":\"Low\",\"risk\":\"Low\"},{\"id\":\"opt-2\",\"label\":\"[Option B]\",\"description\":\"[Brief description]\",\"pros\":[\"Pro 1\"],\"cons\":[\"Con 1\",\"Con 2\"],\"effort\":\"Medium\",\"risk\":\"Medium\"}],\"linkedIssueIds\":[]}",
"version": 1
}
}
Rules
- Always provide at least 2 options (even for binary yes/no decisions)
- Each option must have at least 1 pro and 1 con
- Effort levels: Low, Medium, High, Very High
- Risk levels: Low, Medium, High, Critical
- Title should be a clear question (e.g., "Should we use Redis or Memcached for caching?")
- Description should provide context and constraints
- If prior decisions exist in workspace notes, reference them
- Status starts as "open" — user decides via the UI
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 · 52 lines · 13 tokens per session scan A bb2019f0efbc
adr-lite is a skill published in the GitHub repository pilotspace/pilot-space (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 507 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…