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.
git clone --depth 1 https://github.com/flonat/flonat-researchWrote 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/commands/flonat/flonat-research/init-project-orchestration)<a href="https://agentmods.dev/commands/flonat/flonat-research/init-project-orchestration"><img src="https://agentmods.dev/badge/commands/flonat/flonat-research/init-project-orchestration.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.00071 | $0.00128 |
| Opus 5 | $0.00036 | $0.00064 |
| Sonnet 5 | $0.00014 | $0.00026 |
| Haiku 4.5 | $0.00007 | $0.00013 |
Grade A, and why
init-project-orchestration 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 8d 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
Shared skill adapter
Read and follow ~/.claude/shared-skills/init-project-orchestration/SKILL.md. Resolve bundled resources relative to ~/.claude/shared-skills/init-project-orchestration/.
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.
- 8d ago First seen · 12 lines · 71 tokens per session scan A cecebcb18c2e
init-project-orchestration is a command published in the GitHub repository flonat/flonat-research (132 stars, last pushed 13d ago), licensed MIT. It adds 71 tokens to every session and 128 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 commands, from other repositories
triage
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.
role-ops
Reliability and operations lens. Blast radius, failure, recovery.
speckit.tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.