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 agents/iloom-ai/iloom-cli/iloom-framework-detectorgit clone --depth 1 https://github.com/iloom-ai/iloom-cliWhat 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.00076 | $0.03608 |
| Opus 5 | $0.00038 | $0.01804 |
| Sonnet 5 | $0.00015 | $0.00722 |
| Haiku 4.5 | $0.00008 | $0.00361 |
Grade A, and why
iloom-framework-detector 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 · 482 lines · 76 tokens per session scan A 5d6abb965cb2
iloom-framework-detector is an agent published in the GitHub repository iloom-ai/iloom-cli (111 stars, last pushed 1mo ago), with no licence file. It adds 76 tokens to every session and 3,608 once invoked, about $0.0004 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 agents, from other repositories
epic-scoper
PLANNING SUBAGENT — scopes ONE epic into an ordered list of stories with disjoint Owned File/Module Scope boundaries, making the epic's stories safe for parallel execution by the story-author subagents that follow. Receives: one epic's requirements slice (from epics.md or the PRD cluster), the architecture document…
readiness-auditor
PLANNING SUBAGENT — independently audits one or more planning artifacts and returns a structured verdict of PASS, CONCERNS, or FAIL with itemized findings. Designed for parallel deployment: spawn one auditor per artifact domain (requirements, architecture, stories) and let the orchestrator merge verdicts. Use when the…
story-author
PLANNING SUBAGENT — compiles ONE story file as a fully source-cited context object in isolation. Receives a single story assignment (epic number, story number, slug, and the shared sharding-context path) and produces one {epic}.{story}.{slug}.story.md that is self-contained (8K tokens) and ready for the orchestrator's…
implementer
Make focused code changes that match the project profile and verification bar.
orchestrator
Coordinate research, implementation, and review using the saved project profile.
researcher
Gather repo context, relevant skills, and source references before implementation.