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/ashtonian/llm-init/adrnpx skills add ashtonian/llm-init --skill adrgit clone --depth 1 https://github.com/ashtonian/llm-initWrote 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/ashtonian/llm-init/adr)<a href="https://agentmods.dev/skills/ashtonian/llm-init/adr"><img src="https://agentmods.dev/badge/skills/ashtonian/llm-init/adr.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.00006 | $0.00467 |
| Opus 5 | $0.00003 | $0.00234 |
| Sonnet 5 | $0.00001 | $0.00093 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
adr 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
Create an Architecture Decision Record (ADR) for a design choice.
Instructions
-
Read existing ADRs in
docs/spec/biz/(files matchingadr-*.md). -
Determine the next ADR number (e.g.,
adr-001,adr-002). -
Discuss the decision with the user:
- What is the context? What forces are at play?
- What options were considered?
- What was decided and why?
- What are the consequences (positive and negative)?
-
Create the ADR at
docs/spec/biz/adr-{NNN}-{slug}.md:
# ADR-{NNN}: {Title}
| Field | Value |
|-------|-------|
| **Status** | proposed / accepted / deprecated / superseded |
| **Date** | {date} |
| **Deciders** | {who was involved} |
| **Supersedes** | {ADR number, if applicable} |
## Context
{What is the issue that we're seeing that is motivating this decision or change?
What forces are at play (technical, business, organizational)?}
## Decision
{What is the change that we're proposing and/or doing?}
## Options Considered
### Option 1: {Name}
- **Pros**: {list}
- **Cons**: {list}
- **Effort**: {low/medium/high}
### Option 2: {Name}
- **Pros**: {list}
- **Cons**: {list}
- **Effort**: {low/medium/high}
## Consequences
### Positive
- {benefit 1}
- {benefit 2}
### Negative
- {tradeoff 1}
- {tradeoff 2}
### Risks
- {risk 1} -- mitigation: {how}
## Related
- {Links to specs, issues, other ADRs}
- Present the ADR to the user for review. Iterate until approved.
- Update
docs/spec/.llm/PROGRESS.mdwith a note about the new ADR.
Decision Topic
$ARGUMENTS
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 · 75 lines · 6 tokens per session scan A 127617e66c44
adr is a skill published in the GitHub repository ashtonian/llm-init (2 stars, last pushed 6mo ago), licensed MIT. It adds 6 tokens to every session and 467 once invoked, about $0.0000 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…