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/coalesce-labs/catalystWrote 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/coalesce-labs/catalyst/github-research)<a href="https://agentmods.dev/agents/coalesce-labs/catalyst/github-research"><img src="https://agentmods.dev/badge/agents/coalesce-labs/catalyst/github-research/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/coalesce-labs/catalyst/github-research"><img src="https://agentmods.dev/badge/agents/coalesce-labs/catalyst/github-research.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.00034 | $0.00746 |
| Opus 5.5 | $0.00014 | $0.00298 |
| Sonnet 5.5 | $0.00007 | $0.00149 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
github-research 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 · 136 lines · 34 tokens per session scan A 530349a6e0ab
github-research is an agent published in the GitHub repository coalesce-labs/catalyst (20 stars, last pushed 17d ago), with no licence file. It adds 34 tokens to every session and 746 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-30.
Other agents, from other repositories
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
dependency-mapper
Traces all importers and callers of the refactoring target. Maps exported symbols to consumers and flags breaking-change risk. Uses batched CodeSift queries.
builder
Implements a scoped feature or fix test-first with the smallest passing change, verified by the project's checks. Use when the design is settled and code needs writing.
security-red-team
Use when reviewing code for security vulnerabilities. Thinks like an attacker. Searches for current CVEs and OWASP Top 10 issues relevant to the tech stack. Invoke for security audits, pre-deployment reviews, or when touching auth, payments, or user data.
security-blue-team
Use after the red team has reported findings. Proposes concrete fixes, hardening measures, and defense-in-depth strategies. Reviews red team findings for false positives and prioritizes remediation by risk.
arch-challenger
Devil's advocate for architecture decisions. Use when proposing a new system design, choosing a technology, or making a significant structural change. Challenges assumptions and proposes alternatives.