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 artivilla/agents-config --skill reclaudegit clone --depth 1 https://github.com/artivilla/agents-configWrote 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/artivilla/agents-config/reclaude)<a href="https://agentmods.dev/skills/artivilla/agents-config/reclaude"><img src="https://agentmods.dev/badge/skills/artivilla/agents-config/reclaude/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/artivilla/agents-config/reclaude"><img src="https://agentmods.dev/badge/skills/artivilla/agents-config/reclaude.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.00030 | $0.00761 |
| Opus 5 | $0.00015 | $0.00380 |
| Sonnet 5 | $0.00006 | $0.00152 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
reclaude 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
reclaude
Refactor CLAUDE.md files to follow progressive disclosure principles.
Prompt
I want you to refactor my CLAUDE.md file to follow progressive disclosure principles.
Follow these steps:
1. Check length
Report the current line count. Flag issues:
- Ideal: <50 lines
- Acceptable: 50-100 lines
- Needs refactoring: >100 lines (move content to
.claude/rules/files)
2. Ensure verification section exists
Check for a ## Verification section with commands Claude can run after making changes. If missing:
- Look in package.json for test/lint/typecheck/build scripts
- Look for Makefile, justfile, or other task runners
- Add a
## Verificationsection with discovered commands
This is critical—Claude performs dramatically better when it can verify its work.
3. Find contradictions
Identify any instructions that conflict with each other. For each contradiction, ask me which version I want to keep.
4. Check for global skill extraction candidates
Look for content that could become a reusable global skill in ~/.claude/skills/:
- Is about a tool/framework (not project-specific)
- Same instructions appear (or would apply) in 2+ projects
- Is substantial (>20 lines)
If found, suggest creating a global skill with name and description.
5. Identify essentials for root CLAUDE.md
Extract only what belongs in the root CLAUDE.md:
- One-line project description
- Package manager (if not npm)
- Non-obvious commands only (skip
npm test,npm run buildif standard) - Links to
.claude/rules/files with brief descriptions - Verification section (always required)
6. Group remaining content
Organize remaining instructions into .claude/rules/ files by category (e.g., TypeScript conventions, testing patterns, API design, Git workflow).
7. Flag for deletion
Identify content that should be removed entirely:
- API documentation — link to external docs instead
- Code examples — Claude can infer from reading source files
- Interface/type definitions — these exist in the code
- Generic advice — "write clean code", "follow best practices"
- Obvious instructions — "use TypeScript for .ts files"
- Redundant info — things Claude already knows
- Too vague — instructions that aren't actionable
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 · 106 lines · 30 tokens per session scan A b2858b1f4aa9
reclaude is a skill published in the GitHub repository artivilla/agents-config (0 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 761 once invoked, about $0.0002 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
workers-best-practices
Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.
find-journalists
Build, refine, dedupe, and enrich small fit-checked journalist lists for newsjack campaigns. Uses the newsjack CLI (preferred) or the medialyst MCP for news search and journalist enrichment, and falls back to a best-effort local mode with no verified contacts; the agent owns how returned data is organized.
story-origin-check
Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.
relevance-coarse-filter
Cheap, high-recall first-pass filter that removes obvious junk from a detector candidate pool before expensive story-origin research and PR judgment. Decides keep, monitoronly, or reject — never ranks, writes angles, verifies dates, or decides whether to pitch.
annotating-task-lineage
Annotate Airflow tasks with data lineage using inlets and outlets. Use when the user wants to add lineage metadata to tasks, specify input/output datasets, or enable lineage tracking for operators without built-in OpenLineage extraction.
ai-visibility-writing
Audit, question, suggest, or fact-preservingly revise a press release, blog post, contributed article, or expert explainer so AI answer systems can more easily retrieve, understand, quote, and cite its useful information. Use when someone asks for AI visibility, AI search, answer-engine, AEO, GEO, AI Overview, or…