Borrowing it
Nothing to install: this file belongs to Firmislabs/firmis-scanner. 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/Firmislabs/firmis-scanner/main/CLAUDE.mdgit clone --depth 1 https://github.com/Firmislabs/firmis-scannerWrote 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/firmislabs/firmis-scanner/claude-md)<a href="https://agentmods.dev/instructions/firmislabs/firmis-scanner/claude-md"><img src="https://agentmods.dev/badge/instructions/firmislabs/firmis-scanner/claude-md.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.00738 | $0.00738 |
| Opus 5 | $0.00369 | $0.00369 |
| Sonnet 5 | $0.00148 | $0.00148 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
firmis-scanner 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 6d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Firmis Scanner - Claude Code Rules (Public Repo)
Repo Structure
This is the PUBLIC open-source repo. It contains M0 + M1 code only.
| Folder | Remote | Repo | Visibility | Content |
|---|---|---|---|---|
~/github/firmis-scanner/ (this) |
origin → firmislabs/firmis-scanner |
PUBLIC | M0 + M1 only | |
~/github/firmis-engine/ |
origin → firmislabs/firmis-engine |
PRIVATE | All code (M0–M5) |
Rules (MANDATORY, NO EXCEPTIONS)
- This repo is PUBLIC. Every commit is visible to the world.
- NEVER add M2+ code here. No fix engine, pentest engine, rugpull detection, monitor, or cloud code.
- NEVER add a remote pointing to
firmis-enginein this folder. - All development happens in
~/github/firmis-engine/. This repo receives cherry-picked public-safe commits only. - Push normally:
git push origin main
Files That Must NEVER Appear Here
src/fix/- Fix enginesrc/pentest/- Pentest enginesrc/rugpull/- Rug pull detectionsrc/monitor/- Runtime monitorsrc/cloud/- Cloud/telemetrysrc/types/fix.ts,src/types/pentest.tssrc/cli/commands/fix.ts,src/cli/commands/pentest.ts,src/cli/commands/monitor.tstest/unit/fix/,test/unit/pentest/,test/unit/rugpull/test/integration/fix-*.test.ts,test/integration/pentest-*.test.ts,test/integration/rugpull-*.test.tstest/fixtures/fix-targets/,test/fixtures/pentest/test/helpers/firmis-lasso-plugin/
Verification
After any cherry-pick, always verify:
ls src/fix src/pentest src/rugpull 2>/dev/null && echo "DANGER: M2 files!" || echo "CLEAN"
Development
- Stack: TypeScript / Node.js ESM / Vitest
- Pre-flight:
npx tsc --noEmit && npx vitest run - Max 50 lines/function, max 300 lines/file
- No
anytypes, explicit return types on exports
Git Commit Rules
- NEVER add
Co-Authored-Bytrailers to commits in this repo. This is a public repo - commit history must show only human authors. - Commit messages should be clean conventional commits (feat/fix/docs/chore/test/refactor).
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.
- 6d ago First seen · 64 lines · 738 tokens per session scan A e7a0bf01df2c
firmis-scanner CLAUDE.md is an instructions file published in the GitHub repository Firmislabs/firmis-scanner (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 738 tokens to every session, about $0.0037 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
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.
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.
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).
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).
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.
spec-kit AGENTS.md
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.