claudeframework: Skill for Claude Code

.claude/skills/scout/SKILL.md

scout is a skill for Claude Code from dixus/claudeframework. It costs 28 tokens per session (3,366 once invoked), scanned A, original, MIT.

A research workflow that checks recent Claude Code updates, community skills, and the project’s existing setup.

In plain words
What is it for?
Use it to review release notes, compare the current framework with newer patterns, track findings over time, and produce a report of optimization opportunities.
Why use it?
It helps find relevant changes and possible improvements without changing project files.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: model in frontmatter; reads .claude/ paths; mentions CLAUDE.md.

This is dixus/claudeframework's own configuration. It tells Claude Code how to work on claudeframework itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claudeframework configures →

Reuse

Borrowing it

Nothing to install: this file belongs to dixus/claudeframework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/dixus/claudeframework/main/.claude/skills/scout/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/dixus/claudeframework

Made for: Claude Code.

Wrote 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.

agentmods badge for scout

README.md
[![agentmods](https://agentmods.dev/badge/skills/dixus/claudeframework/scout/github.svg)](https://agentmods.dev/skills/dixus/claudeframework/scout)
Your own site
<a href="https://agentmods.dev/skills/dixus/claudeframework/scout"><img src="https://agentmods.dev/badge/skills/dixus/claudeframework/scout/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for scout

Your own site · 80×15
<a href="https://agentmods.dev/skills/dixus/claudeframework/scout"><img src="https://agentmods.dev/badge/skills/dixus/claudeframework/scout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,366 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.03366
Opus 5.5 $0.00011 $0.01346
Sonnet 5.5 $0.00006 $0.00673
Haiku 4.5 $0.00003 $0.00337

Measured 1mo ago against content hash 6390086e220e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

.claude/skills/scout/SKILL.md · 303 lines

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

  1. Read CLAUDE.md for current framework context
  2. Read all skill files in .claude/skills/ to understand current capabilities
  3. Read .claude/context/lessons.md if it exists (.claude/rules/instincts.md is auto-loaded by Claude Code)
  4. Find the most recent previous scout report: glob .claude/references/blogs/scout-*.md and read the latest one. This is used in the diff phase later. If none exists, skip diffing.
  5. Read metrics trend. If .claude/metrics-scout.csv exists and contains 2+ rows, compute the trend direction for findings_count and action_items_count across 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.

Read the full file on GitHub · 303 lines

Changes

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.

  1. 1mo ago Changed 6390086e220e
  2. 2mo ago First seen · 303 lines · 28 tokens per session scan A 50ac5b086b2a

Subscribe to this mod's changes

scout is a skill published in the GitHub repository dixus/claudeframework (10 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 3,366 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens