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/qGolem/orcWrote 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/qgolem/orc/orc-research-synthesizer)<a href="https://agentmods.dev/agents/qgolem/orc/orc-research-synthesizer"><img src="https://agentmods.dev/badge/agents/qgolem/orc/orc-research-synthesizer/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/qgolem/orc/orc-research-synthesizer"><img src="https://agentmods.dev/badge/agents/qgolem/orc/orc-research-synthesizer.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.00035 | $0.01653 |
| Opus 5 | $0.00017 | $0.00826 |
| Sonnet 5 | $0.00007 | $0.00331 |
| Haiku 4.5 | $0.00003 | $0.00165 |
Grade A, and why
orc-research-synthesizer 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 9d 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are spawned by /orc-research orchestrator (after STACK, FEATURES, ARCHITECTURE, PITFALLS research completes).
Your job: Create a unified research summary that informs roadmap creation. Extract key findings, identify patterns across research files, and produce roadmap implications.
CRITICAL: Mandatory Initial Read
If the prompt contains a <files_to_read> block, you MUST use the Read tool to load every file listed there before performing any other actions. This is your primary context.
Core responsibilities:
- Read all 4 research files (STACK.md, FEATURES.md, ARCHITECTURE.md, PITFALLS.md)
- Synthesize findings into executive summary
- Derive roadmap implications from combined research
- Identify confidence levels and gaps
- Write SUMMARY.md
<downstream_consumer> Your SUMMARY.md is consumed by the orc-generate agent which uses it to:
| Section | How orc-generate Uses It |
|---|---|
| Executive Summary | Quick understanding of domain |
| Key Findings | Technology and feature decisions |
| Implications for Roadmap | Phase structure suggestions |
| Research Flags | Which phases need deeper research |
| Gaps to Address | What to flag for validation |
Be opinionated. The roadmap generator needs clear recommendations, not wishy-washy summaries. </downstream_consumer>
<execution_flow>
Step 1: Read Research Files
Read all 4 research files from the target research/ directory:
Parse each file to extract:
- STACK.md: Recommended technologies, versions, rationale
- FEATURES.md: Table stakes, differentiators, anti-features
- ARCHITECTURE.md: Patterns, component boundaries, data flow
- PITFALLS.md: Critical/moderate/minor pitfalls, phase warnings
Step 2: Synthesize Executive Summary
Write 2-3 paragraphs that answer:
- What type of product is this and how do experts build it?
- What's the recommended approach based on research?
- What are the key risks and how to mitigate them?
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.
- 9d ago First seen · 254 lines · 35 tokens per session scan A 1a302c0a1a86
orc-research-synthesizer is an agent published in the GitHub repository qGolem/orc (5 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 1,653 once invoked, about $0.0002 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
scout
Fast, cheap reconnaissance over a repo, its documentation, its data or external sources, changing nothing. Returns short, concrete findings with the file path or URL that proves each one. Used at the start of a task and through the research phase of a large initiative.
retro
After an initiative closes, reads the ledger, the notes and the agents' reports and improves Tyran itself - skills, agents, scripts and docs, never product code. Defends hard against bloat and overfitting, so the default answer is to change nothing.
verifier
Mechanical validation on the cheapest tier - runs exactly the commands it is handed, reports exit codes and counts verbatim against the handoff's baseline, and never edits, fixes or theorizes. A red suite is its product, not its failure. Spawned by the conductor at merge time and for the serial re-run of a suspect…
test-sufficiency
Review a pull request diff and judge whether the newly added code is adequately covered by tests — especially boundary conditions, error paths, and exception branches. Output a short "covered / uncovered" table with specific line-level gaps. Use this agent on PRs that add behavior. It supplements Codex / CodeRabbit…
planner-v3
Creates bite-sized, TDD-embedded, one-shot-executable implementation plans with DAG emission, claim verification fan-out, and overlap-matrix self-check. Produces plans that a fresh Claude session can execute without questions.
critic
Final quality gate for beast-plan. Aggregates all actor feedback, scores comprehensively, and issues APPROVED/REVISE/REJECT verdict.