Borrowing it
Nothing to install: this file belongs to benwu95/prospec. 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/benwu95/prospec/main/.agents/skills/submit-issue/SKILL.mdgit clone --depth 1 https://github.com/benwu95/prospecWrote 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/skills/benwu95/prospec/submit-issue)<a href="https://agentmods.dev/skills/benwu95/prospec/submit-issue"><img src="https://agentmods.dev/badge/skills/benwu95/prospec/submit-issue/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/skills/benwu95/prospec/submit-issue"><img src="https://agentmods.dev/badge/skills/benwu95/prospec/submit-issue.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.00077 | $0.01700 |
| Opus 5.5 | $0.00031 | $0.00680 |
| Sonnet 5.5 | $0.00015 | $0.00340 |
| Haiku 4.5 | $0.00008 | $0.00170 |
Grade A, and why
submit-issue 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 2mo 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Submit Issue Skill
Open a GitHub issue for the prospec repo in the house format. The format below is derived from the merged issue corpus (#179–#196, #203–#208); this skill executes the pattern, and newer merged issues outrank it when they disagree.
Language
The issue body is Traditional Chinese (Taiwan) — a house convention, same rationale as PR bodies:
the Constitution's [MUST] Language Policy is defined over repo paths, and an issue body is not one
(see prospec/CONSTITUTION.md → Language Policy, mirrored in AGENTS.md). The title stays
English in conventional-commit form, as do code identifiers, file paths, and technical terms inside
the body. Never append an AI attribution footer. The repo uses no labels — do not add any.
Scope discipline — one issue per change
Size each issue so it maps to exactly one prospec change / one PR (/prospec-new-story registers
it via prospec change story --issue "#NN"). A body that needs two unrelated 方案 groups or two
independent AC sets is two issues — split them and cross-link the series. Defects discovered
mid-flight go to a change artifact or a new issue, never into frozen planning docs.
Preconditions
-
ghis authenticated as an account with write access. With more than one account logged in, the active one can silently be the wrong one, andghthen fails with a misleading error:gh api user -q .login # must be able to write to this repo gh auth switch --hostname github.com --user <account> # only if it is not -
Evidence in hand. Every number, file path, and behavioral claim in the body must come from something actually observed — a measurement, an archived record, a review finding, a repro run.
Step-by-step
1. Draft the body to a scratch file
Write it somewhere git-ignored (e.g. .tasks/issue-<slug>.md or the session scratchpad), following
the format below. Show the draft for sign-off before creating unless the user already approved
the content in conversation — an issue is public the moment it exists.
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.
- 2mo ago First seen · 128 lines · 77 tokens per session scan A 559a3702b93d
submit-issue is a skill published in the GitHub repository benwu95/prospec (6 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 1,700 once invoked, about $0.0003 per session on Opus 5.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.
submit-issue compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| submit-issuebenwu95/prospec | Skill | 6 | yesterday | MIT | A | 77 | Claude Code, Codex |
| ospec-goalclawplays/ospec | Skill | 390 | 2mo ago | MIT | A | 29 | Codex |
| ospecclawplays/ospec | Skill | 390 | 2mo ago | MIT | A | 26 | Claude Code, Codex |
| ospec-changeclawplays/ospec | Skill | 390 | 2mo ago | MIT | A | 18 | Codex |
| openspec-bulk-apply-changeintent-driven-dev/openspec-schemas | Skill | 116 | 2mo ago | MIT | A | 30 | OpenCode |
| deliverfiratcand/forge | Skill | 14 | 3mo ago | MIT | A | 64 | Claude Code, Codex |
| wrap-upfiratcand/forge | Skill | 14 | 3mo ago | MIT | A | 56 | Claude Code, Codex |