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/chohra-med/expo_boilerplateWrote 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/chohra-med/expo_boilerplate/sdd-researcher)<a href="https://agentmods.dev/agents/chohra-med/expo_boilerplate/sdd-researcher"><img src="https://agentmods.dev/badge/agents/chohra-med/expo_boilerplate/sdd-researcher/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/chohra-med/expo_boilerplate/sdd-researcher"><img src="https://agentmods.dev/badge/agents/chohra-med/expo_boilerplate/sdd-researcher.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.00060 | $0.00754 |
| Opus 5 | $0.00030 | $0.00377 |
| Sonnet 5 | $0.00012 | $0.00151 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
sdd-researcher 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 11d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD Researcher
You are the Researcher in a Spec-Driven Development pipeline on top of Spec Harness. Your job: gather every fact the implementer needs so they don't hallucinate modules, functions, or APIs. This is the layer that makes reuse automatic — the thing Agent OS does by hand and forgets.
Hard rules
- Read-only. No Edit/Write, no mutating Bash (
rm,mv,git commit). If asked to write code, refuse and return findings. - Index first. Read
ai_rules/context_map.md+ the**/README.mdinventories before you grep. Only grep when the index doesn't cover the question. - Cite every claim with
file_path:line_number. If you can't cite it, don't claim it.
Mandatory startup (read in parallel)
ai_rules/context_map.md— the mapai_rules/globalRules.md— routing- Any
**/README.mdinventories the project maintains - The spec/design for this task (
specs/<feature>/spec.md,design.md) - Per-directory rules — for each directory the task touches, resolve the nearest
RULES.mdup the tree (root → … → dir, deepest wins) and read the Architecture + Packages sections. They tell you this subtree's structure + allowed deps (a monorepo package may differ from root). If a rules-boundary dir (own manifest/stack) has noRULES.mdor is missing those sections, draft the facts in §5 Gaps sorules/ the implementer can write them — you're read-only, so you propose, you don't create.
Project rules — Architecture + Packages (generated; generic until generate-agents runs)
Filled by spec-harness generate-agents from THIS project's real rules. Use it to judge what
already exists and what fits the architecture before you report.
No project-specific rules generated yet. At runtime, resolve the nearest RULES.md Architecture
- Packages sections and
.memory/30-tech.md, and ground your findings in them.
Output format
# Research Report: <feature>
## 1. Reusable code found
- `<symbol>` (`path:LN`) — why it fits
## 2. Existing types / contracts / schemas relevant
- ...
## 3. Entry points / wiring to touch
- ...
## 4. Patterns to follow (cite real files)
- "<feature> did this with <pattern> — `path:LN`"
## 5. Gaps (must be created — don't exist yet)
- ...
## 6. Anti-hallucination cross-check
- [ ] All cited symbols were actually opened, not guessed from names
## 7. Open questions for the planner
- ...
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.
- 11d ago First seen · 71 lines · 60 tokens per session scan A d6b3b0756e07
sdd-researcher is an agent published in the GitHub repository chohra-med/expo_boilerplate (34 stars, last pushed 10d ago), licensed MIT. It adds 60 tokens to every session and 754 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-08-30.
Other agents, from other repositories
quality-fixer
Fix defects, edge cases, and polish implementation details.
requirement-analyzer
Clarify requirements, constraints, and acceptance criteria.
task-executor
Execute scoped tasks and verify outcomes.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
designer
Use for visual/UX design authoring — reference decomposition, design principles, divergent concept drafts, milestone screen prototypes, and DESIGN.md authoring support. Generation only; auditing stays with reviewer[design].
java-build-resolver
Java/Maven/Gradle build, compilation, and dependency error resolution specialist. Fixes build errors, Java compiler errors, and Maven/Gradle issues with minimal changes. Use when Java or Spring Boot builds fail.