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 agentmods add instructions/clearfunction/cf-devtools/claude-mdgit clone --depth 1 https://github.com/clearfunction/cf-devtoolsWhat 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 | $0.01613 | $0.01613 |
| Opus 5 | $0.00807 | $0.00807 |
| Sonnet 5 | $0.00323 | $0.00323 |
| Haiku 4.5 | $0.00161 | $0.00161 |
Grade A, and why
cf-devtools CLAUDE.md 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 yesterday.
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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CF DevTools - Development Guidelines
Project Overview
WHAT: Claude Code plugin with 2 skills (slidev-presentations, 1password-direnv-secrets) and 8 slash commands.
WHY: Production-ready developer workflows for Clear Function's enterprise clients - presentations and secrets management.
HOW: Skills in skills/, commands in commands/. Test locally before committing.
Quick Commands
# Install locally for testing
/plugin add /path/to/cf-devtools
# Verify plugin structure
ls -la .claude-plugin/
cat .claude-plugin/plugin.json | jq .
# Test a skill activates (in Claude Code)
"Create a presentation about React hooks" # Should trigger slidev-presentations
"Set up 1Password with direnv" # Should trigger 1password-direnv-secrets
# Test a command works
/slidev:new test topic
/secrets:init
# Validate before commit
find skills -name "SKILL.md" -exec head -10 {} \; # Check frontmatter
wc -l skills/*/SKILL.md # Check line counts (<500)
Skill Authoring Best Practices
When creating or modifying skills in this repository, follow these guidelines based on Anthropic's official skill authoring best practices.
The Golden Rule: Progressive Disclosure
SKILL.md is a table of contents, not the encyclopedia.
Skills use progressive disclosure - showing just enough information for Claude to decide what to do next, then revealing details as needed. This means:
- SKILL.md provides an overview and navigation
- Detailed content lives in separate reference files
- Claude loads files only when needed, saving context tokens
skill-name/
├── SKILL.md # Overview + navigation (keep under 500 lines)
├── references/
│ ├── detailed-guide.md # Comprehensive documentation
│ ├── api-reference.md # API details
│ └── examples.md # Input/output examples
└── scripts/ # Executable utilities
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.
- yesterday First seen · 208 lines · 1,613 tokens per session scan A b74d1332892c
cf-devtools CLAUDE.md is an instructions file published in the GitHub repository clearfunction/cf-devtools (5 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 1,613 tokens to every session, about $0.0081 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.