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/tickets-forge-dev/loop-lang/claude-mdgit clone --depth 1 https://github.com/tickets-forge-dev/loop-langWhat 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.00327 | $0.00327 |
| Opus 5 | $0.00163 | $0.00163 |
| Sonnet 5 | $0.00065 | $0.00065 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
loop-lang 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 9 lines · 327 tokens per session scan A eaf2ed7d19b8
loop-lang CLAUDE.md is an instructions file published in the GitHub repository tickets-forge-dev/loop-lang (11 stars, last pushed 1mo ago), with no licence file. It adds 327 tokens to every session, about $0.0016 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
truthmark AGENTS.md
Instructions for merlinhu1/truthmark, covering authority, documentation scope, product boundary, rules and instruction surface boundary.
coco-workflow CLAUDE.md
Instructions for skullninja/coco-workflow, covering claude.md -- coco, project overview, architecture, key files and tracker (lib/tracker.sh).
super-dev copilot-instructions.md
Instructions for shangyankeji/super-dev, covering super dev ide rules (vscode-copilot), positioning, runtime contract, first-response contract and local knowledge contract.
slipway AGENTS.md
Instructions for signalridge/slipway, covering slipway agent principles, user owns the process, investigate before clarifying, report, do not certify and maintain the whole surface.
slipway CLAUDE.md
Instructions for signalridge/slipway: Read AGENTS.md. It is the single principle file for this repository, and it applies to Claude Code exactly as written.
RepoResident AGENTS.md
Instructions for ychamel/RepoResident: Agent entry point: read CLAUDE.md in full — it is the operating manual — then follow its Session protocol. Everything else (state, workflows, project knowledge) is routed from there via the .agent/ directory.