Borrowing it
Nothing to install: this file belongs to tosin2013/helmdeck. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tosin2013/helmdeck/main/CLAUDE.mdgit clone --depth 1 https://github.com/tosin2013/helmdeckWrote 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/instructions/tosin2013/helmdeck/claude-md)<a href="https://agentmods.dev/instructions/tosin2013/helmdeck/claude-md"><img src="https://agentmods.dev/badge/instructions/tosin2013/helmdeck/claude-md/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/instructions/tosin2013/helmdeck/claude-md"><img src="https://agentmods.dev/badge/instructions/tosin2013/helmdeck/claude-md.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.00363 | $0.00363 |
| Opus 5.5 | $0.00145 | $0.00145 |
| Sonnet 5.5 | $0.00073 | $0.00073 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
helmdeck 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 1mo 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
Helmdeck
Read docs/integrations/SKILLS.md for helmdeck-specific instructions when using tools.
Read docs/integrations/pack-demo-playbook.md for example prompts and expected outputs.
When development surfaces something noteworthy, draft a blog post
If your work in this repo turns up something the broader engineering audience would learn from — a quantified cost result, an unexpected interaction between two subsystems, an architectural insight, or a friction story with a clean fix — propose a blog draft alongside the implementation using website/blog/_template.md.
Don't gate on whether it ships. Drafts with draft: true cost nothing to land and zero to discard, but they capture the finding while it's fresh. The blog's value compounds with cadence; treat draft posts as a normal output of development work, not a separate marketing track.
See CONTRIBUTING.md §"Other contribution types" for the workflow.
If the post is research-flavored, also update /research
Helmdeck is, in practice, a research project that ships as software. The pattern is real: hard implementation work — the kind that takes time and money to push through — is what produces the findings worth publishing. Don't lose them.
If the blog post you're drafting is research-flavored (the finding generalizes beyond the immediate fix — a new empirical pattern, an architectural insight, a quantified cost or capability result), add an entry to website/src/pages/research.md in the same change. One-line summary + link to the post / ADR / production change that landed it.
The /research page is the durable, citeable surface that turns "trust me, we're doing research" into "click any entry." It's load-bearing for grant applications and external citations — keep it current.
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.
- 1mo ago First seen · 21 lines · 363 tokens per session scan A 224027198cfe
helmdeck CLAUDE.md is an instructions file published in the GitHub repository tosin2013/helmdeck (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 363 tokens to every session, about $0.0015 per session on Opus 5.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
vscode buildNext.instructions.md
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
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, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.