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 0xDarkMatter/claude-mods --skill auto-skillgit clone --depth 1 https://github.com/0xDarkMatter/claude-modsWrote 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/0xdarkmatter/claude-mods/auto-skill)<a href="https://agentmods.dev/skills/0xdarkmatter/claude-mods/auto-skill"><img src="https://agentmods.dev/badge/skills/0xdarkmatter/claude-mods/auto-skill.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.1 | $0.00038 | $0.02576 |
| Opus 5 | $0.00019 | $0.01288 |
| Sonnet 5 | $0.00008 | $0.00515 |
| Haiku 4.5 | $0.00004 | $0.00258 |
Grade C, and why
auto-skill scanned grade C with 2 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 8d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- `auto-skill pending` — `cat ~/.claude/auto-skill/pending.log` (or show Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls ~/.claude/skills/ 2>/dev/null; ls .claude/skills/ 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-Skill
Evaluate the current session and create a reusable skill from complex workflows. Enforces the Agent Skills specification and quality gates.
When This Triggers
- User runs
/auto-skill - Stop hook suggests it after a complex session (8+ mutating ops across 4+ tool types)
- User says "save this as a skill", "capture this workflow", etc.
Command Router
Parse arguments after auto-skill (or /auto-skill):
| User says | Action |
|---|---|
auto-skill (no args) |
Run the full evaluation procedure below |
auto-skill off |
Disable globally: touch ~/.claude/auto-skill.disable and confirm |
auto-skill on |
Enable globally: rm -f ~/.claude/auto-skill.disable and confirm |
auto-skill off --project |
Disable for this project: mkdir -p .claude && touch .claude/auto-skill.disable |
auto-skill on --project |
Enable for this project: rm -f .claude/auto-skill.disable |
auto-skill status |
Show current state (see Status section below) |
auto-skill pending |
Show all entries in ~/.claude/auto-skill/pending.log (past suggestions the user may have missed) |
auto-skill clear |
Truncate ~/.claude/auto-skill/pending.log after confirming with user |
Status
When the user runs auto-skill status, check and report:
# Global toggle
[ -f "$HOME/.claude/auto-skill.disable" ] && echo "Global: OFF" || echo "Global: ON"
# Project toggle
[ -f ".claude/auto-skill.disable" ] && echo "Project: OFF" || echo "Project: ON"
# Hook scripts installed?
[ -x "$HOME/.claude/auto-skill/track-tools.sh" ] && echo "Hooks: installed" || echo "Hooks: not installed"
# Active session tracking?
ls /tmp/claude_autoskill_* 2>/dev/null | head -1 && echo "Tracking: active" || echo "Tracking: idle"
Report results in a brief table.
Procedure
Step 1: Evaluate the Session
Review the conversation history in the current session. Ask yourself:
- Was this a multi-step workflow? (3+ distinct actions, not just read/search)
- Is it reusable? Would someone do this again - in this project or another?
- Is it novel? Does an existing skill already cover this? Check with:
ls ~/.claude/skills/ 2>/dev/null; ls .claude/skills/ 2>/dev/null - Is it teachable? Can it be described as a clear procedure with steps?
What ships with it
6 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.
- 8d ago First seen · 286 lines · 38 tokens per session scan C 9516cdc3f996
auto-skill is a skill published in the GitHub repository 0xDarkMatter/claude-mods (33 stars, last pushed 15d ago), licensed MIT. It adds 38 tokens to every session and 2,576 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (reads agent configuration directories, enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
thinking-theory-of-constraints
When throughput or latency is pipeline-limited, identify the single binding constraint and exploit, subordinate, elevate, then recheck—ignore non-constraints.
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
foundation-models
On-device LLM integration using Apple's Foundation Models framework. Use when implementing AI text generation, structured output, or tool calling.
analytics-interpretation
Interpret app metrics and make data-driven decisions. Covers DAU/MAU, retention, LTV, ARPU, App Store Connect analytics, AARRR funnel analysis, cohort analysis, and diagnostic decision trees. Use when user wants to understand their metrics, diagnose problems, or build a data-driven growth plan.
app-namer
Turn an app idea into validated, App-Store-ready name candidates. Use when the user says "name my app", "what should I call it", "app name ideas", "help me name this app", "is this name available", or needs to pick a brandable, ownable name before reserving it in App Store Connect.
in-app-events
Generates In-App Event metadata templates for App Store Connect — event names, descriptions, badge types, image specs, and deep link configuration. Use when creating events for App Store visibility, engagement campaigns, or seasonal promotions.