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/luongnv89/asm/claude-mdgit clone --depth 1 https://github.com/luongnv89/asmWrote 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/luongnv89/asm/claude-md)<a href="https://agentmods.dev/instructions/luongnv89/asm/claude-md"><img src="https://agentmods.dev/badge/instructions/luongnv89/asm/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 | $0.01430 | $0.01430 |
| Opus 5 | $0.00715 | $0.00715 |
| Sonnet 5 | $0.00286 | $0.00286 |
| Haiku 4.5 | $0.00143 | $0.00143 |
Grade A, and why
asm 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 4d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
agent-skill-manager (asm) — a TypeScript CLI plus ink/React TUI that manages
Agent Skills installed for Claude Code, Codex, Gemini, and OpenClaw.
Critical commands
npm install # postinstall no-ops when CI or ASM_SKIP_POSTINSTALL is set
npm run build # tsx scripts/build.ts -> dist/ (gitignored)
CI=true npm test # unit suite — the command of record
npm run test:coverage # v8 coverage for src/ — measurement only, no fail gate
npm run typecheck # tsc --noEmit
npm run lint # eslint over src/
npm run lint:site # eslint over website-src/src
npm run test:e2e # tests/e2e/ — NOT covered by `npm test`
npm start # run the TUI from source
npm test is vitest run src/, and that argument is a substring filter on the
test path, not a directory — website-src/src/__tests__/ matches it too, so
npm run test:site is a subset of npm test, not a separate leg. Only
tests/e2e/ is excluded. Measured timings and evidence: docs/AGENT_ENVIRONMENT.md.
npm run test:coverage is vitest run --coverage src/ with
@vitest/coverage-v8 (4.x, matching current vitest). It reports line and
branch percentages for src/ product files only (test files excluded). There
is no coverage threshold and no CI fail gate — measurement before
improvement (F-TEST-003 / #438). Vitest 4 remaps V8 coverage via AST, so the
live number may differ from the #438 baseline below; keep coverage.include.
Coverage baseline (2026-08-19, src/, v8, CI=true npm run test:coverage,
2113 tests):
- Lines: 60.61% (12598/20783)
- Branches: 82.52% (3406/4127)
M3's coverage target is bound to max(60%, baseline + 20pp):
- Lines:
max(60%, 80.61%)= 80.61% - Branches:
max(60%, 102.52%)= 100% (formula saturates at 100)
Node and npm must satisfy package.json engines — node ">=18 <23", npm
">=9". Mind the upper bound: CONTRIBUTING.md and docs/DEVELOPMENT.md still
state a floor with no ceiling, and engines is the one that is correct.
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.
- 4d ago First seen · 100 lines · 1,430 tokens per session scan A f6c519716088
asm CLAUDE.md is an instructions file published in the GitHub repository luongnv89/asm (908 stars, last pushed today), licensed MIT. It adds 1,430 tokens to every session, about $0.0072 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-30.
Other instructions, from other repositories
newsjack AGENTS.md
AGENTS.md instructions for elvisun/newsjack, covering agents.md, repo shape, canonical boundaries, minimal memory and discovery doctrine.
newsjack CLAUDE.md
Claude Code instructions for elvisun/newsjack: Load AGENTS.md before editing this repo — follow it.
agent-toolkit AGENTS.md
AGENTS.md instructions for LandonSchropp/agent-toolkit, covering project overview, commands, architecture, project structure and interactive command workflow.
claude-skills CLAUDE.md
Claude Code instructions for troykelly/claude-skills, covering claude code development instructions, foundational principle, the contract, research-first methodology and the rule.
claude-email-assistant CLAUDE.md
Instructions for marian-kamenistak/claude-email-assistant, covering email assistant, working discipline, your job, email management and triage.
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).