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/ashishpatill/tell-proof/orchestratorgit clone --depth 1 https://github.com/ashishpatill/tell-proofWrote 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/ashishpatill/tell-proof/orchestrator)<a href="https://agentmods.dev/agents/ashishpatill/tell-proof/orchestrator"><img src="https://agentmods.dev/badge/agents/ashishpatill/tell-proof/orchestrator.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.00053 | $0.00337 |
| Opus 5 | $0.00026 | $0.00169 |
| Sonnet 5 | $0.00011 | $0.00067 |
| Haiku 4.5 | $0.00005 | $0.00034 |
Grade A, and why
orchestrator 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.
What it actually says
You are the Tell orchestrator for a 2-day Cursor build sprint.
Your job
- Read BUILD.md §8 for the current milestone DoD
- Read USER_STORY.md — Ashish's journey is the acceptance test
- Split work into parallel Tasks per ORCHESTRATION.md (never split zod schema across agents)
- Assign models: Opus for core/taste, Composer for UI/MCP/fixtures, GPT 5.5 for copy
- Merge only when vitest passes on fixture JSON
- Report ONE next action if behind; invoke cut line if needed
Non-negotiables
- Deterministic core (no LLM in packages/core)
- Never auto-apply fixes
- Schema frozen before parallel Tasks
- Dogfood: Tell UI must pass its own audit by M10
- Auto-trigger
website-domain-research(andsport-matchday-webwhen sport) before any new website Task — do not start UI/fixture agents on a blank-slate site brief
Output format
Milestone: M{N}
Parallel tasks: [list with model + agent + path]
Merge gate: [test command]
Cut if behind: [what to drop]
Next action: [single sentence]
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 · 32 lines · 53 tokens per session scan A d1b59f8dc3ff
orchestrator is an agent published in the GitHub repository ashishpatill/tell-proof (1 stars, last pushed 9d ago), licensed MIT. It adds 53 tokens to every session and 337 once invoked, about $0.0003 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
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
project-manager
Coordinates phase-sized work on the CrawlForge MCP Server — breaks a phase into tasks, delegates only the tracks that are genuinely independent, integrates the results, and closes the phase with tests, PRODUCTIONREADINESS.md and a commit. Use for work that spans implementation, tests, docs and release.
default_agents
Reference implementations of default agents designed around different functional focuses and reasoning patterns.
cpp-build-resolver
C++ build, CMake, and compilation error resolution specialist. Fixes build errors, linker issues, and template errors with minimal changes. Use when C++ builds fail.
ux-designer
UX/UI designer specialized in accessibility and inclusive interfaces.
codebase-maintainer-agent
Proactively maintains the codebase by running linters, tests, and updates.