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/ltplus-ag/ifc-lite/claude-mdgit clone --depth 1 https://github.com/LTplus-AG/ifc-liteWrote 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/ltplus-ag/ifc-lite/claude-md)<a href="https://agentmods.dev/instructions/ltplus-ag/ifc-lite/claude-md"><img src="https://agentmods.dev/badge/instructions/ltplus-ag/ifc-lite/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.00034 | $0.00034 |
| Opus 5 | $0.00017 | $0.00017 |
| Sonnet 5 | $0.00007 | $0.00007 |
| Haiku 4.5 | $0.00003 | $0.00003 |
Grade A, and why
ifc-lite 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 5d 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
Claude Code Guidelines for ifc-lite
See AGENTS.md for the full agent guidelines used by all AI assistants in this project.
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.
- 5d ago First seen · 4 lines · 34 tokens per session scan A 7c260929e08e
ifc-lite CLAUDE.md is an instructions file published in the GitHub repository LTplus-AG/ifc-lite (359 stars, last pushed yesterday), licensed MPL-2.0. It adds 34 tokens to every session, about $0.0002 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
grida AGENTS.md
Instructions for gridaco/grida, covering hi robots, welcome to the grida project, project structure, languages, frameworks, tools, infrastructures, documentation and the rust engine — moved to gridaco/nothing.
massing AGENTS.md
AGENTS.md instructions for ibuilder/massing, covering agents.md, cursor cloud specific instructions, what the update script already did, services (all run from source in dev) and node 24 gotcha (important).
massing CLAUDE.md
Claude Code instructions for ibuilder/massing, covering project: massing, what this is, non-negotiables, stack and build order.
nothing AGENTS.md
AGENTS.md instructions for gridaco/nothing, covering the laws (bind every change), setup, commands, check (each crate must pass independently) and tests.
brometal AGENTS.md
Instructions for ericdrowell/brometal, covering brometal — notes for coding agents working on this repo, layout, commands, inside packages/website and adding a shader function.
brometal CLAUDE.md
Instructions for ericdrowell/brometal, covering working on brometal, always update the changelog, only edit the root file, verify before claiming and order of operations.