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 Xakki/ai-agents-skills --skill setup-claudegit clone --depth 1 https://github.com/Xakki/ai-agents-skillsWrote 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/xakki/ai-agents-skills/setup-claude)<a href="https://agentmods.dev/skills/xakki/ai-agents-skills/setup-claude"><img src="https://agentmods.dev/badge/skills/xakki/ai-agents-skills/setup-claude/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/xakki/ai-agents-skills/setup-claude"><img src="https://agentmods.dev/badge/skills/xakki/ai-agents-skills/setup-claude.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.00037 | $0.01230 |
| Opus 5 | $0.00018 | $0.00615 |
| Sonnet 5 | $0.00007 | $0.00246 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade B, and why
setup-claude scanned grade B with 1 finding 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
[ ] PreToolUse + Bash: block rm -rf, git push --force, direct docker/npm bypassing make — low risk Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Claude Code in this repository
Universal template, stack-agnostic. All artifacts live locally in the repo and under git.
1. Sources (mandatory — WebFetch before work)
Canonical domain: code.claude.com/docs/en/*. Full URL list with per-page descriptions → reference.md.
If 404 → WebSearch site:code.claude.com <topic>. Ignore third-party blogs.
2. Discovery — Phase 1 (no file writes)
git log --oneline -30, active branches, manifests (package.json,composer.json,go.mod,Makefile,docker-compose.yml)- Existing
CLAUDE.md(managed → user → project),.claude/rules/,.claude/agents/,.claude/skills/,.claude/commands/,.mcp.json,AGENTS.md - README/CONTRIBUTING/TODO — extract team process and no-touch zones only
- Stack map, monolith vs modules, legacy vs new; Makefile quality
- Skip:
vendor/,node_modules/,*_data/,dist/,build/, binaries
Report ≤ 30 lines: stacks, existing Claude config, proposed agents/skills/MCP/rules, Makefile plan, hook options (§4 below). Wait for ok. Alternative: suggest /init as starting point, then refine.
3. Deliverables — Phase 2 (after confirmation)
| Artifact | Key constraint |
|---|---|
CLAUDE.md |
≤ 200 lines; only what can't be read from code; mandate make <target> for all ops |
.claude/rules/*.md |
Optional; use paths: frontmatter to scope to subtrees |
.claude/agents/*.md |
name + description required; explicit tools:; narrow scope |
.claude/skills/<name>/SKILL.md |
≤ 500 lines; happy-path only; bulk detail → neighbor files |
.mcp.json |
Project-specific only; list in enabledMcpjsonServers; use claude mcp add |
.claude/settings.json |
Commit; settings.local.json → .gitignore; deny→ask→allow (first match) |
Makefile |
Required; create if absent; make help with ##@ groups; all ops via make |
Full frontmatter fields, settings.json template, and Makefile skeleton → reference.md.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 88 lines · 37 tokens per session scan B 031e8956de54
setup-claude is a skill published in the GitHub repository Xakki/ai-agents-skills (6 stars, last pushed 19d ago), licensed MIT. It adds 37 tokens to every session and 1,230 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
openpanel
Query self-hosted OpenPanel analytics — funnel counts, unique users, breakdowns by os/country/path, raw events. Use whenever analytics numbers are needed: funnel conversion, visitor counts, event counts over a window, period-over-period deltas, "how many signups/checkouts/sessions", or any /darkflow:analytics-review…
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.
taiyi-diagram-c4
A code-scanning tool that builds C4 architecture documents from a repository. It separates facts observed in the code from conclusions inferred about the design and uses Mermaid diagrams as the source format.
docs
Use when documentation generally needs to catch up with a branch before pushing or merging, covering internal developer docs, external customer-facing docs, and release notes together — "update the docs", "do a docs pass before I merge", "make sure everything's documented". Prefer this when no single documentation…
chart-rendering
Render governed Kun charts and tables from structured data for trustworthy comparison and lookup.
legal-risk-assessment
Structure legal-risk reviews by issue, rule source, likelihood, impact, evidence, uncertainty, controls, and escalation.