RepoBrain is a repository knowledge engine that lets coding agents ask grounded questions about a codebase and receive answers linked to source files and lines. It is for developers using Claude Code, Cursor, Codex, Windsurf, and other AI coding tools. Catalogue add-ons extend its commands, instructions, skills, rules, plugin, and hook workflows.
Borrowing it
Nothing to install: this file belongs to study8677/repobrain. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/study8677/repobrain/main/.github/prompts/openspec-archive.prompt.mdgit clone --depth 1 https://github.com/study8677/repobrainWrote 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/commands/study8677/repobrain/openspec-archive)<a href="https://agentmods.dev/commands/study8677/repobrain/openspec-archive"><img src="https://agentmods.dev/badge/commands/study8677/repobrain/openspec-archive/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/commands/study8677/repobrain/openspec-archive"><img src="https://agentmods.dev/badge/commands/study8677/repobrain/openspec-archive.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.00010 | $0.00428 |
| Opus 5 | $0.00005 | $0.00214 |
| Sonnet 5 | $0.00002 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
openspec-archive 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 yesterday.
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.
Copies of this mod
8 near-identical copies found in the catalogue:
- openspec-archive — 98% identical, 5 lines differ
- openspec-archive — 97% identical, 7 lines differ
- OpenSpec: Archive — 95% identical, 7 lines differ
- archive — 95% identical, 5 lines differ
- OpenSpec: Archive — 95% identical, 7 lines differ
- archive — 95% identical, 5 lines differ
- archive — 95% identical, 5 lines differ
- OpenSpec: Archive — 95% identical, 5 lines differ
What it actually says
$ARGUMENTS
Guardrails
- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
- Keep changes tightly scoped to the requested outcome.
- Refer to
openspec/AGENTS.md(located inside theopenspec/directory—runls openspecoropenspec updateif you don't see it) if you need additional OpenSpec conventions or clarifications.
Steps
- Determine the change ID to archive:
- If this prompt already includes a specific change ID (for example inside a
<ChangeId>block populated by slash-command arguments), use that value after trimming whitespace. - If the conversation references a change loosely (for example by title or summary), run
openspec listto surface likely IDs, share the relevant candidates, and confirm which one the user intends. - Otherwise, review the conversation, run
openspec list, and ask the user which change to archive; wait for a confirmed change ID before proceeding. - If you still cannot identify a single change ID, stop and tell the user you cannot archive anything yet.
- If this prompt already includes a specific change ID (for example inside a
- Validate the change ID by running
openspec list(oropenspec show <id>) and stop if the change is missing, already archived, or otherwise not ready to archive. - Run
openspec archive <id> --yesso the CLI moves the change and applies spec updates without prompts (use--skip-specsonly for tooling-only work). - Review the command output to confirm the target specs were updated and the change landed in
changes/archive/. - Validate with
openspec validate --strictand inspect withopenspec show <id>if anything looks off.
Reference
- Use
openspec listto confirm change IDs before archiving. - Inspect refreshed specs with
openspec list --specsand address any validation issues before handing off.
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.
- yesterday First seen · 27 lines · 10 tokens per session scan A 5fd91b05e5e8
openspec-archive is a command published in the GitHub repository study8677/repobrain (1,325 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 428 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-09-08.
Other commands, from other repositories
research-init
Initialize a research project with Zotero-integrated literature review. Creates or audits project-scoped sources, generates research question cards, and only writes a research proposal when the evidence gate passes.
update-memory
Check and update CLAUDE.md memory based on changes to skills, commands, agents, and hooks.
promote
Draft research promotion content and optionally publish approved X posts.
modernization-flow
Workflow for converting, modernizing, upgrading, or re-architecting code (e.g. C++→Java, monolith→microservices), etc.
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).