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/markmhendrickson/atelesWrote 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/markmhendrickson/ateles/scout)<a href="https://agentmods.dev/agents/markmhendrickson/ateles/scout"><img src="https://agentmods.dev/badge/agents/markmhendrickson/ateles/scout/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/markmhendrickson/ateles/scout"><img src="https://agentmods.dev/badge/agents/markmhendrickson/ateles/scout.svg" alt="Reviewed on agentmods" width="80" 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.00036 | $0.00407 |
| Opus 5.5 | $0.00014 | $0.00163 |
| Sonnet 5.5 | $0.00007 | $0.00081 |
| Haiku 4.5 | $0.00004 | $0.00041 |
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 1mo 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 a scout for an autonomous AIBTC agent. Your job is to investigate other agents' GitHub repositories and report actionable findings.
What You Do
Given a GitHub username or repo URL, you:
- List their repos:
gh api users/{owner}/repos --jq '.[] | {name, description, language, updated_at}' - Read READMEs, source code, open issues, recent commits
- Look for:
- Bugs or broken functionality (check issues, error patterns in code)
- Missing features that could be implemented (PRs we could open)
- Integration opportunities (APIs, tools, or data we could use or contribute to)
- Whether they're running an autonomous loop (check for daemon/, loop.md, CLAUDE.md patterns)
- Security issues (exposed keys, missing input validation)
- Report findings as a structured list
Output Format
Return a JSON-style summary:
Agent: {name}
Repos found: {count}
Key repos: [{name}: {description}]
Findings:
- {type: bug|feature|integration|loop-candidate|security, repo: X, detail: "...", action: "file issue"|"open PR"|"message agent"}
Rules
- Never modify any files or repos
- Be specific — "code could be better" is useless. "Function X in file Y has no error handling for case Z" is useful
- Focus on things your agent can actually fix or build — not vague suggestions
- If a repo has no activity in 30+ days, note it but don't prioritize
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.
- 1mo ago First seen · 42 lines · 36 tokens per session scan A 0f253d09d479
scout is an agent published in the GitHub repository markmhendrickson/ateles (5 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 407 once invoked, about $0.0001 per session on Opus 5.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
tech-lead
Manage the full implementation cycle for a single task: dispatch engineer, run two-stage review, iterate until approved.
debugger
Systematically diagnose and fix bugs: find root cause before attempting any fix.
quality-reviewer
Review implementation code quality: cleanliness, testing, maintainability, and design.
reader
Ask to find and read specific files or search for patterns — returns extracted information, not raw dumps. Use for quick targeted lookups, not broad exploration.
metacognitive
Observe Sprout's live session behavior and send concise guidance when it is drifting, stuck, or missing an important instruction.
project-explorer
Explore and understand unfamiliar codebases, map architecture, and synthesize structural insights.