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 skills add paulo-yamagishi/claude-code-setup --skill add-core-guidegit clone --depth 1 https://github.com/paulo-yamagishi/claude-code-setupWrote 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/paulo-yamagishi/claude-code-setup/add-core-guide)<a href="https://agentmods.dev/skills/paulo-yamagishi/claude-code-setup/add-core-guide"><img src="https://agentmods.dev/badge/skills/paulo-yamagishi/claude-code-setup/add-core-guide/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.
<a href="https://agentmods.dev/skills/paulo-yamagishi/claude-code-setup/add-core-guide"><img src="https://agentmods.dev/badge/skills/paulo-yamagishi/claude-code-setup/add-core-guide.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00014 | $0.00403 |
| Opus 5 | $0.00007 | $0.00201 |
| Sonnet 5 | $0.00003 | $0.00081 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
add-core-guide 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 10d 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
Add Core Guide
Create a new core/{topic}-guide.md file for the topic specified in $ARGUMENTS.
Steps
-
Validate topic: Confirm
core/$ARGUMENTS-guide.mddoes not already exist. If it does, report and stop. -
Fetch official docs: Use WebFetch to read
https://docs.anthropic.com/en/docs/claude-codepages relevant to the topic for authoritative content. -
Study existing guides: Read 2-3 files in
core/to extract the consistent structure:- Title format:
# Topic Guide - Section pattern: overview → key concepts → configuration → examples → troubleshooting → cross-references
- Style: imperative, concrete examples, valid JSON in code blocks, language-agnostic
- Length: under 300 lines
- Title format:
-
Generate the guide:
- Follow the extracted structure exactly
- Use only verified information from official docs
- Include at least 2 concrete JSON or bash code block examples
- All JSON must be valid — no comments, no trailing commas
- All settings keys and hook events must match official documentation
- Keep language-agnostic — no framework-specific advice
-
Add cross-references:
- Link to related core guides using relative paths:
../core/{related}-guide.md - Grep other guides for mentions of the new topic and note where a backlink would help
- Link to related core guides using relative paths:
-
Verify: Re-read the generated file and confirm:
- Valid JSON in all code blocks
- Under 300 lines
- No duplicate of existing content in other guides
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.
- 10d ago First seen · 45 lines · 14 tokens per session scan A d9ae2514ca0c
add-core-guide is a skill published in the GitHub repository paulo-yamagishi/claude-code-setup (2 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 403 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.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…