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 commands/tractorjuice/arckit-codex/arckit.finopsgit clone --depth 1 https://github.com/tractorjuice/arckit-codexWrote 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/tractorjuice/arckit-codex/arckit.finops)<a href="https://agentmods.dev/commands/tractorjuice/arckit-codex/arckit.finops"><img src="https://agentmods.dev/badge/commands/tractorjuice/arckit-codex/arckit.finops.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.00015 | $0.02736 |
| Opus 5 | $0.00008 | $0.01368 |
| Sonnet 5 | $0.00003 | $0.00547 |
| Haiku 4.5 | $0.00002 | $0.00274 |
Grade A, and why
arckit.finops 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 yesterday.
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.
- yesterday First seen · 348 lines · 15 tokens per session scan A e9920cd55d2d
arckit.finops is a command published in the GitHub repository tractorjuice/arckit-codex (16 stars, last pushed 2d ago), with no licence file. It adds 15 tokens to every session and 2,736 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
finops
Create FinOps strategy with cloud cost management, optimization, governance, and forecasting.
eu-cloud-sovereignty
You are helping an enterprise architect generate an EU Cloud Sovereignty Framework Assessment for an organisation procuring, specifying, or evaluating cloud services against the European Commission's EU Cloud Sovereignty Framework (v1.2.1, October 2025). The framework supplements security assurance (SecNumCloud, EUCS…
nl-cloud
You are helping an enterprise architect generate a Rijksbreed Cloudbeleid Compliance Assessment for Dutch central government (Rijksoverheid) cloud use. The Herziening rijksbreed cloudbeleid 2026 (Ministerie van Economische Zaken en Klimaat, 3 July 2026, definitief) is the governing policy — it applies to all central…
operationalize
Create operational readiness pack with support model, runbooks, DR/BCP, on-call, and handover documentation.
gcp-research
Research Google Cloud services and architecture patterns using Google Developer Knowledge MCP for authoritative guidance.
nl-exit
You are helping an enterprise architect produce a Cloud Exit Plan required under clause 3.2 of the Herziening rijksbreed cloudbeleid 2026 (Ministerie van Economische Zaken en Klimaat, 3 July 2026, definitief). The exit plan is mandatory, documented, and self-tested wherever materieel publiek cloudgebruik applies, and…