agentmods.dev

repobrain: Command for Claude Code

.github/prompts/openspec-proposal.prompt.md

openspec-proposal is a command for Claude Code, GitHub Copilot from study8677/repobrain. It costs 11 tokens per session (542 once invoked), scanned A, original, MIT.

A command that creates the documents for a proposed OpenSpec change. OpenSpec is a structured way to describe software changes before implementation.

In plain words
What is it for?
Use it to inspect the current project, create a change proposal and task list, and record design or specification updates without writing implementation code.
Why use it?
It keeps planning separate from coding, asks about unclear requirements, and limits the proposal to the requested scope before approval.

Command for Claude CodeGitHub Copilot

Written for Claude Code and GitHub Copilot: $ARGUMENTS substitution, but also a Copilot chat mode or prompt. Also seen: mentions AGENTS.md.

This is study8677/repobrain's own configuration. It tells Claude Code and GitHub Copilot how to work on repobrain itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything repobrain configures →

Part of the repobrain plugin — 4 skills, 7 commands, 1 hook shipped together

not rated 1.3krepo +1 today A scan 11 tokens original MIT
View source ↗ study8677/repobrain deepwiki.com
About the project

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.

study8677/repobrain · 1,325 stars · on GitHub · deepwiki.com

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/study8677/repobrain/main/.github/prompts/openspec-proposal.prompt.md
Clone the repo
git clone --depth 1 https://github.com/study8677/repobrain

Made for: Claude Code, GitHub Copilot.

Or install repobrain, the plugin that ships this one along with the rest of its 4 skills, 7 commands, 1 hook.

Wrote 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.

agentmods badge for openspec-proposal

README.md
[![agentmods](https://agentmods.dev/badge/commands/study8677/repobrain/openspec-proposal/github.svg)](https://agentmods.dev/commands/study8677/repobrain/openspec-proposal)
Your own site
<a href="https://agentmods.dev/commands/study8677/repobrain/openspec-proposal"><img src="https://agentmods.dev/badge/commands/study8677/repobrain/openspec-proposal/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.

agentmods 80×15 button for openspec-proposal

Your own site · 80×15
<a href="https://agentmods.dev/commands/study8677/repobrain/openspec-proposal"><img src="https://agentmods.dev/badge/commands/study8677/repobrain/openspec-proposal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 542 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00011 $0.00542
Opus 5 $0.00005 $0.00271
Sonnet 5 $0.00002 $0.00108
Haiku 4.5 $0.00001 $0.00054

Measured yesterday against content hash 6695bcd70d4c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

openspec-proposal 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.

Origin

Copies of this mod

8 near-identical copies found in the catalogue:

.github/prompts/openspec-proposal.prompt.md · 28 lines

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 the openspec/ directory—run ls openspec or openspec update if you don't see it) if you need additional OpenSpec conventions or clarifications.
  • Identify any vague or ambiguous details and ask the necessary follow-up questions before editing files.
  • Do not write any code during the proposal stage. Only create design documents (proposal.md, tasks.md, design.md, and spec deltas). Implementation happens in the apply stage after approval.

Steps

  1. Review openspec/project.md, run openspec list and openspec list --specs, and inspect related code or docs (e.g., via rg/ls) to ground the proposal in current behaviour; note any gaps that require clarification.
  2. Choose a unique verb-led change-id and scaffold proposal.md, tasks.md, and design.md (when needed) under openspec/changes/<id>/.
  3. Map the change into concrete capabilities or requirements, breaking multi-scope efforts into distinct spec deltas with clear relationships and sequencing.
  4. Capture architectural reasoning in design.md when the solution spans multiple systems, introduces new patterns, or demands trade-off discussion before committing to specs.
  5. Draft spec deltas in changes/<id>/specs/<capability>/spec.md (one folder per capability) using ## ADDED|MODIFIED|REMOVED Requirements with at least one #### Scenario: per requirement and cross-reference related capabilities when relevant.
  6. Draft tasks.md as an ordered list of small, verifiable work items that deliver user-visible progress, include validation (tests, tooling), and highlight dependencies or parallelizable work.
  7. Validate with openspec validate <id> --strict and resolve every issue before sharing the proposal.

Reference

  • Use openspec show <id> --json --deltas-only or openspec show <spec> --type spec to inspect details when validation fails.
  • Search existing requirements with rg -n "Requirement:|Scenario:" openspec/specs before writing new ones.
  • Explore the codebase with rg <keyword>, ls, or direct file reads so proposals align with current implementation realities.
Changes

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.

  1. yesterday First seen · 28 lines · 11 tokens per session scan A 6695bcd70d4c

Subscribe to this mod's changes

openspec-proposal is a command published in the GitHub repository study8677/repobrain (1,325 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 542 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.

Claude CodePlanningWriting and docscode-searchcodex-clideveloper-toolsmcp-serverwindsurf
Related

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.

Galaxy-Dawn/claude-scholar · 40 tokens

update-memory

Check and update CLAUDE.md memory based on changes to skills, commands, agents, and hooks.

Galaxy-Dawn/claude-scholar · 21 tokens

promote

Draft research promotion content and optionally publish approved X posts.

Galaxy-Dawn/claude-scholar · 13 tokens

modernization-flow

Workflow for converting, modernizing, upgrading, or re-architecting code (e.g. C++→Java, monolith→microservices), etc.

griddynamics/rosetta · 36 tokens

ui-aqa-flow-test-report-analysis

Phase 7 Test Report Analysis of ui-aqa-flow.

griddynamics/rosetta · 19 tokens

api-aqa-flow-execution-and-report-analysis

Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).

griddynamics/rosetta · 28 tokens