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/dixus/claudeframework/scoutnpx skills add dixus/claudeframework --skill scoutgit clone --depth 1 https://github.com/dixus/claudeframeworkWrote 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/dixus/claudeframework/scout)<a href="https://agentmods.dev/skills/dixus/claudeframework/scout"><img src="https://agentmods.dev/badge/skills/dixus/claudeframework/scout.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.00028 | $0.03366 |
| Opus 5 | $0.00014 | $0.01683 |
| Sonnet 5 | $0.00006 | $0.00673 |
| Haiku 4.5 | $0.00003 | $0.00337 |
Grade A, and why
scout 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.
How it starts
The opening of the file, as written. The whole thing — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search the web for recent Claude Code developments and compare against the current framework. Report optimization opportunities without modifying any files.
$ARGUMENTS is optional. Pass --quick to search only (no page fetching) — returns titles and links for manual review.
Steps
- Read CLAUDE.md for current framework context
- Read all skill files in
.claude/skills/to understand current capabilities - Read
.claude/context/lessons.mdif it exists (.claude/rules/instincts.mdis auto-loaded by Claude Code) - Find the most recent previous scout report: glob
.claude/references/blogs/scout-*.mdand read the latest one. This is used in the diff phase later. If none exists, skip diffing. - Read metrics trend. If
.claude/metrics-scout.csvexists and contains 2+ rows, compute the trend direction forfindings_countandaction_items_countacross the last 3 scout runs (increasing / decreasing / stable). Store as a one-line summary for the report header. If fewer than 2 scout rows exist, note "First/second run — no trend data."
Release notes phase (always runs first)
Fetch the official Claude Code changelog directly — do not rely on search for this:
a. WebFetch https://docs.anthropic.com/en/docs/claude-code/changelog
b. If that fails, try: WebFetch https://code.claude.com/docs/en/changelog
c. If both fail, fall back to WebSearch: "Claude Code" changelog site:anthropic.com
Extract all entries from the last 60 days. For each entry, note:
- Version number and date
- New features, new CLI flags, new skill frontmatter fields
- New hook events or hook types
- Breaking changes or deprecations
- New tool capabilities
Compare each entry against the current framework: does it affect any of our skills, hooks, or settings? Flag anything that does.
Actionable mapping: For each flagged entry, map it to a concrete change target: which skill file and what to change (e.g., "add maxTurns: 15 to 3_fix/SKILL.md frontmatter"), or which rule file to create/update in .claude/rules/. If the change doesn't map to any skill or rule, note it as "informational only" — do not propose writing it to a knowledge file.
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 · 303 lines · 28 tokens per session scan A 50ac5b086b2a
scout is a skill published in the GitHub repository dixus/claudeframework (10 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 3,366 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…