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/chaitanya299/orient/flow-tracergit clone --depth 1 https://github.com/Chaitanya299/OrientWrote 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/agents/chaitanya299/orient/flow-tracer)<a href="https://agentmods.dev/agents/chaitanya299/orient/flow-tracer"><img src="https://agentmods.dev/badge/agents/chaitanya299/orient/flow-tracer.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.00019 | $0.00273 |
| Opus 5 | $0.00010 | $0.00137 |
| Sonnet 5 | $0.00004 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
flow-tracer 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 4d 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.
- 4d ago First seen · 28 lines · 19 tokens per session scan A f99ced825a48
flow-tracer is an agent published in the GitHub repository Chaitanya299/Orient (8 stars, last pushed 7d ago), with no licence file. It adds 19 tokens to every session and 273 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-08-31.
Other agents, from other repositories
spec-debugger
Fixes issues when Tester or Reviewer reject an implementation. Fresh perspective on problems the Implementer couldn't solve.
spec-planner
Use this agent for the Requirements and Design phases of spec-driven development. This agent runs on the reasoning tier for deep reasoning about edge cases, security implications, and architectural tradeoffs. Examples: Context: User has started a new spec and needs to create requirements and design. user: "I need to…
spec-scanner
Scans a codebase using LLM-driven heuristics to detect framework, patterns, entities, and registration points. Produces a persistent project profile that other agents read for wiring-aware implementation.
spec-tester
Verifies that implemented tasks actually work. Uses Playwright for UI testing, runs test suites, and only marks Verified: yes after real verification.
spec-acceptor
Performs user acceptance testing by mapping completed tasks back to requirements and verifying traceability, non-functional requirements, and overall completeness. Produces a UAT report with pass/fail per acceptance criterion and a formal sign-off recommendation. Does NOT re-run functional tests (the spec-tester…
spec-tasker
Use this agent to break down a completed spec design into implementation tasks. This agent runs on the standard tier for fast, structured task generation. Examples: Context: User has completed requirements and design, now needs tasks. user: "The requirements and design are done, now break it down into tasks"…