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 skills/benwu95/prospec/prospec-knowledge-generatenpx skills add benwu95/prospec --skill prospec-knowledge-generategit 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/prospec-knowledge-generate)<a href="https://agentmods.dev/skills/benwu95/prospec/prospec-knowledge-generate"><img src="https://agentmods.dev/badge/skills/benwu95/prospec/prospec-knowledge-generate.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.00071 | $0.04631 |
| Opus 5 | $0.00036 | $0.02315 |
| Sonnet 5 | $0.00014 | $0.00926 |
| Haiku 4.5 | $0.00007 | $0.00463 |
Grade A, and why
prospec-knowledge-generate 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 today.
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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prospec Knowledge Generate Skill
Activation
When triggered, briefly describe:
- That you'll read raw-scan.md to understand the project structure
- You'll autonomously decide module boundaries using the configured granularity strategy
- Each module gets exactly one README.md in Recipe-First format (≤100 lines)
- You'll populate prospec/index.md (with the Progressive Knowledge Loading Strategy section) and _conventions.md
Language Policy
Write each generated document in the language the Constitution's Language Policy rule assigns to its path — change artifacts and their archived summaries in the project's artifact language, the trust zone (Knowledge base, Feature Specs, index) in English. One skill run may write both. Keep code, identifiers, technical terms, and git commit messages in English.
CLI Prerequisite (required)
The prospec CLI is a required file for this skill — its deterministic steps call
prospeccommands. Probe BEFORE any other step; there is no manual fallback.
- Run
prospec --version(Bash). - Command not found / not executable → STOP. Ask the user to install the prospec standalone
executable — the one-click installer script from the project README (macOS/Linux
install.sh, Windowsinstall.ps1) or a release binary from GitHub Releases; prospec is NOT published to npm. Then re-run this skill. - Version older than 2.1.0 → STOP. Report the installed vs required version and ask the user to upgrade, then re-run this skill.
Hand-executing a CLI-owned mutation is NEVER the fallback — that re-introduces the nondeterministic serialization this contract exists to remove.
Startup Loading
- [STABLE] Read
prospec/ai-knowledge/_conventions.md— if exists - [STABLE] Read
prospec/ai-knowledge/_module-readme-conventions.mdandprospec/ai-knowledge/_diagram-conventions.md— the canonical module-README structure and diagram rules to generate against (Step 4 generates directly against this canonical file — it is not restated here) - [STABLE] Read
prospec/CONSTITUTION.md— if exists - [DYNAMIC] Ensure
prospec/ai-knowledge/raw-scan.mdis current, then read it — first runprospec knowledge init --raw-scan-only(deterministic, no LLM; creates it if absent) so READMEs generate against the real current structure.module-map.yamlmust already exist (init bootstrap) - [DYNAMIC] Read
prospec/index.md— if exists - [DYNAMIC] Read
.prospec.yaml→ checkknowledge.strategy(auto|architecture|domain|package) andknowledge.token_budget
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.
- today Changed · +2 lines 8e3fd7cd5227
- 4d ago First seen · 257 lines · 71 tokens per session scan A 95eacf9a72da
prospec-knowledge-generate is a skill published in the GitHub repository benwu95/prospec (5 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 4,631 once invoked, about $0.0004 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 skills, from other repositories
ospec-goal
Create or advance a full OSpec goal using the current document, task graph, worker, review, and evidence workflow.
ospec
Document-driven OSpec workflow for initialization, change/goal routing, validation, archiving, and durable project knowledge.
ospec-change
Create or advance a lightweight OSpec change using the classic fast workflow.
review-spd
Findings-first code review workflow for AI coding agents. Use when the user asks to review uncommitted changes, commits in a date range, or a branch compared to the main branch / PR-style diff. Focuses on bugs, regressions, correctness risks, missing tests, security/data-safety issues, and other behavior-changing…
deep-discuss
结构化深度讨论 Skill，用于与用户进行多轮问题分析和方案设计。当用户描述一个问题现象、故障表现、 技术困惑、方案选择困难，或明确说"讨论一下"、"帮我分析"、"我遇到一个问题"、"你觉得怎么样"、 "帮我想想"、"我在纠结"时，必须使用本 skill。当用户提供了一段描述（可能附带截图）并期望深入分析 而非直接给答案时，也应触发本 skill。即使用户只是抛出一个现象描述没有明确提问，也要使用本 skill 来引导结构化思考。不要在简单的事实查询（"X是什么"）或明确的执行指令（"帮我写个脚本"）上触发。.
spec-driven-develop
Automates pre-development workflow for large-scale complex tasks. Use when the user mentions "rewrite", "migrate", "overhaul", "refactor entire project", "transform", "rebuild in [language]", "spec-driven", or describes any large-scale project transformation that requires planning before coding. Also triggers on…