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/masrisystems/dot-agentsWrote 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/masrisystems/dot-agents/echo-developer)<a href="https://agentmods.dev/agents/masrisystems/dot-agents/echo-developer"><img src="https://agentmods.dev/badge/agents/masrisystems/dot-agents/echo-developer/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/masrisystems/dot-agents/echo-developer"><img src="https://agentmods.dev/badge/agents/masrisystems/dot-agents/echo-developer.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.00026 | $0.00227 |
| Opus 5.5 | $0.00010 | $0.00091 |
| Sonnet 5.5 | $0.00005 | $0.00045 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
echo-developer 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.
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.
- 1mo ago First seen · 22 lines · 26 tokens per session scan A 78eb37fd6f3d
echo-developer is an agent published in the GitHub repository masrisystems/dot-agents (0 stars, last pushed 1mo ago), with no licence file. It adds 26 tokens to every session and 227 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-09-03.
Other agents, from other repositories
issue-worker
Lands one GitHub issue as its own pull request, or repairs one open pull request, alone in a worktree. Spawned by github-flow:dispatch and github-flow:shift.
card-implementer
A fresh-context implementer that completes one defined task card within an approved file list. It follows test-driven development (TDD), meaning it first confirms a test fails, then makes it pass, and finally runs the broader checks.
part-implementer
Craft implement phase worker. Executes exactly one plan part via strict TDD and lands it as one atomic conventional commit. Spawned by the craft implement phase — do not auto-select.
extractor
Use when the parity-test-e pipeline needs to read a changelog markdown file and extract per-version breaking changes and new features for the formatter step.
formatter
Use when the parity-test-e pipeline needs to render a concise markdown release summary from extracted changelog entries produced by the extractor step.
implementer
Implement tasks via TDD and commit small changes.