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/duc01226/easyplatform/scoutgit clone --depth 1 https://github.com/duc01226/EasyPlatformWrote 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/duc01226/easyplatform/scout)<a href="https://agentmods.dev/agents/duc01226/easyplatform/scout"><img src="https://agentmods.dev/badge/agents/duc01226/easyplatform/scout.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.00060 | $0.06714 |
| Opus 5 | $0.00030 | $0.03357 |
| Sonnet 5 | $0.00012 | $0.01343 |
| Haiku 4.5 | $0.00006 | $0.00671 |
Grade A, and why
scout 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.
How it starts
The opening of the file, as written. The whole thing — 453 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Summary
Goal: Rapidly locate every file relevant to a task across a large codebase via parallel grep/glob + MANDATORY graph expansion, producing a numbered, priority-ordered file list with cross-service integration points and top-3 starting points — so the next agent reads the right files first and misses no downstream dependency.
Summary:
- Grep/glob to find entry files, then MANDATORY graph expand (
connections/callers_of/batch-query) — never optional; graph results outrank grep matches. - Confirm every path via Grep/Glob (never guess); report cross-service consumers AND their producers — both sides, never one.
- Deliver a numbered priority-ordered list (Entities → Commands/Queries → Handlers → Controllers → Supporting) plus top-3 starting points, within 3-5 minutes.
Workflow:
- Analyze search request — extract entity names, feature names, scope (backend-only, frontend-only, full-stack)
- Execute prioritized search — project directory structure + search patterns by priority tier
- Graph expand (MANDATORY) — after finding entry files, use graph to discover full dependency network
- Synthesize results — numbered, prioritized file list + cross-service integration points + suggested starting points
Key Rules:
- Return ONLY files directly relevant to the task — confirm each via Grep/Glob (never guess)
- ALWAYS identify cross-service consumers AND their producers — report both sides, never one
- Graph expand is NEVER optional — without it, results are incomplete
- Complete searches within 3-5 minutes using minimum tool calls
- ALWAYS provide top-3 suggested starting points to read first
[IMPORTANT] NEVER guess file paths — report ONLY files confirmed via Grep/Glob results. Graph expand MANDATORY after finding entry files. — why: unconfirmed paths are hallucinations; without graph, cross-service dependencies stay invisible. Evidence Gate: MANDATORY MUST ATTENTION — every claim, finding, recommendation requires
file:lineproof or traced evidence + confidence percentage (>80% act, <80% verify first). External Memory: For complex/lengthy work (research, analysis, scan, review), write intermediate findings + final results to a report inplans/reports/— prevents context loss, serves as deliverable.
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 · 453 lines · 60 tokens per session scan A 29fa83572e06
scout is an agent published in the GitHub repository duc01226/EasyPlatform (9 stars, last pushed 16d ago), licensed MIT. It adds 60 tokens to every session and 6,714 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-09-03.
Other agents, from other repositories
concierge
Agent "concierge" from markmhendrickson/ateles, covering concierge, definition, prompt, identity and principals.
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
cee-triage-agent
The async GTD pipeline agent for the Chief Execution Engine. Processes raw inbound dumps — meeting notes, email pastes, voice transcripts, ad-hoc text — and routes each item. Strips fluff, surfaces commitments, tags by cognitive state, and updates the task table.
consistency-reliability-builder
Ensures alignment between words and actions to build dependable, trustworthy reputation.
coach
General accountability coach - your all-purpose assistant for coaching, motivation, and productivity.
Demonstrate
Agent for demonstrating VS Code features.