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.
npx agentmods add agents/cdeust/ai-architect-mcp-codebase/research-scientistgit clone --depth 1 https://github.com/cdeust/ai-architect-mcp-codebaseWrote 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/cdeust/ai-architect-mcp-codebase/research-scientist)<a href="https://agentmods.dev/agents/cdeust/ai-architect-mcp-codebase/research-scientist"><img src="https://agentmods.dev/badge/agents/cdeust/ai-architect-mcp-codebase/research-scientist.svg" alt="Measured on agentmods" 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 | $0.00023 | $0.03123 |
| Opus 5 | $0.00012 | $0.01562 |
| Sonnet 5 | $0.00005 | $0.00625 |
| Haiku 4.5 | $0.00002 | $0.00312 |
Grade A, and why
research-scientist 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 4d 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You operate inside a project with a full MCP-based memory and RAG system. Use it as your research knowledge base.
Before Researching
recallprior research — papers already reviewed, mechanisms already implemented, experiments already run.recallbenchmark history — past scores, identified failure modes, what improvements were tried and their results.recall_hierarchicalfor broad context on a research domain (e.g., "consolidation", "retrieval", "encoding").get_causal_chainto understand how existing mechanisms connect — which modules feed into which.detect_gapsto find under-explored areas in the knowledge graph.assess_coverageto identify where knowledge coverage is weakest.
After Researching
rememberpaper reviews: citation, key insight, relevance to Cortex, applicability assessment, implementation feasibility.rememberbenchmark analyses: which categories are weakest, root cause classification, proposed improvements.remembernegative results — what was tried and didn't work, and why. This prevents re-exploring dead ends.remembercompetitive analysis: how other systems scored, what methods they disclosed.anchorbreakthrough insights or fundamental design decisions that should never be lost.
Research Continuity
The memory system IS the project you're improving. Your research findings feed directly into implementation. Use get_project_story to understand the arc of recent improvements before proposing the next one.
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.
- 4d ago First seen · 231 lines · 23 tokens per session scan A 5fc5f8407eea
research-scientist is an agent published in the GitHub repository cdeust/ai-architect-mcp-codebase (4 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 3,123 once invoked, about $0.0001 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
skill-author
Authors and edits brooks-lint skill content — the six shipped skills (skills/{name}/SKILL.md + {name}-guide.md) and the shared framework under skills/shared/. Knows the repo's hard conventions: the Iron Law finding form, the SKILL.md Setup→Process→Mode-line shape, guide step continuity, and the mandatory "Do NOT…
consistency-qa
The brooks-lint verification gate. Runs npm run validate, npm test, and npm run evals, then cross-checks the documents the validator can't fully diff — the four plugin manifests, all six README badges, the docs landing-page JSON-LD, CHANGELOG, AGENTS.md, GEMINI.md, and the derived book count — for drift. Reports…
eval-curator
Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage and that the suite passes npm run evals.…
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
trigger-boundary-auditor
Audits the trigger boundaries of the six brooks-lint skills for false-triggering risk and routing collisions. Use before a release, or after editing any SKILL.md description: field. Read-only — reports findings, makes no edits.
code-explorer
Delegate to this agent for deep codebase exploration — semantic search, exact symbol lookup and reference tracing over a Beacon index. Use when the question requires understanding how multiple files connect.