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/openprose/prose/open-prosenpx skills add openprose/prose --skill open-prosegit clone --depth 1 https://github.com/openprose/proseWrote 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/openprose/prose/open-prose)<a href="https://agentmods.dev/skills/openprose/prose/open-prose"><img src="https://agentmods.dev/badge/skills/openprose/prose/open-prose.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.00133 | $0.06767 |
| Opus 5 | $0.00067 | $0.03383 |
| Sonnet 5 | $0.00027 | $0.01353 |
| Haiku 4.5 | $0.00013 | $0.00677 |
Grade A, and why
open-prose 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 — 413 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenProse Skill
OpenProse has five load-bearing pieces:
| Piece | File | Role |
|---|---|---|
| Contract Markdown | contract-markdown.md |
Human-readable *.prose.md source format |
| Forme | forme.md |
Semantic dependency-injection container that wires contracts |
| Prose VM | prose.md |
Execution engine that runs responsibilities, functions, and pinned execution blocks |
| ProseScript | prosescript.md |
Imperative scripting layer for ### Execution blocks and pattern delegation |
| Responsibility Runtime | responsibility-runtime.md |
Responsibility-Oriented Architecture: standing goals, the reconciler, and compile/serve doctrine |
Use Contract Markdown when authors want declarations and auto-wiring. Use ProseScript when authors want to pin choreography: order, loops, conditionals, parallelism, retries, and explicit function calls.
First 90 Seconds
After activation, choose the narrowest path that matches the user's intent:
| User Intent | Load First | Then Load If Needed |
|---|---|---|
| Explain OpenProse or answer "how do I..." | help.md |
examples/README.md, then one focused example |
| Initialize or compose an OpenProse program | guidance/tenets.md |
guidance/authoring.md, then run std/ops/compose |
Run a .prose.md responsibility or function |
contract-markdown.md |
state/README.md and the selected backend (state/filesystem.md by default); forme.md if responsibilities must be wired (### Requires → ### Maintains); prose.md to execute |
| Inspect or upgrade source layout | changelog.md |
contract-markdown.md, prosescript.md if migration details require them |
Write a new .prose.md responsibility or function |
contract-markdown.md |
guidance/tenets.md, guidance/authoring.md |
| Write pinned choreography | prosescript.md |
contract-markdown.md if inside ### Execution |
Compile or run a .png/.svg brief (a typed image) |
visual-source.md |
forme.md and compiler/index.prose.md to resolve + compile |
| Lint or review a responsibility or function | contract-markdown.md |
forme.md for multi-responsibility wiring; guidance/authoring.md for design review |
| Work on Responsibility Runtime, responsibility-oriented source, the reconciler, compile, or serve semantics | responsibility-runtime.md |
compiler/index.prose.md, compiler/ir-v0.md, concepts/responsibility.md, concepts/reconciler.md, forme.md |
| Install or update dependencies | deps.md |
contract-markdown.md only if dependency references are ambiguous |
| Debug a completed run | prose.md |
state/README.md and the run's backend doc; then std/evals/inspector if available |
What ships with it
60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agent-onboarding.md 3.9 KB
- changelog.md 12 KB
- compiler/index.prose.md 18 KB
- compiler/ir-v0.md 14 KB
- concepts/README.md 806 B
- concepts/reconciler.md 9.6 KB
- concepts/responsibility.md 8.4 KB
- contract-markdown.md 33 KB
- deps.md 15 KB
- examples/agent-observatory/.gitignore 74 B
- examples/agent-observatory/README.md 4.3 KB
- examples/agent-observatory/src/agent-dashboard-html.prose.md 1.1 KB
- examples/agent-observatory/src/agent-index-markdown.prose.md 1.3 KB
- examples/agent-observatory/src/concept-clusterer.prose.md 1.7 KB
- examples/agent-observatory/src/runtime-adapter.prose.md 1.7 KB
- examples/agent-observatory/src/runtime-watch.prose.md 2.4 KB
- examples/agent-observatory/src/session-ledger.prose.md 2.0 KB
- examples/agent-observatory/src/session-summary.prose.md 1.5 KB
- examples/agent-observatory/src/session-to-prose.prose.md 2.4 KB
- examples/agent-observatory/src/workstream-index.prose.md 2.2 KB
- examples/auto-pocock/README.md 9.6 KB
- examples/auto-pocock/src/auto-pocock.prose.md 6.0 KB
- examples/auto-pocock/src/decide-plan.prose.md 1.9 KB
- examples/auto-pocock/src/ensure-skills.prose.md 2.8 KB
- examples/auto-pocock/src/grill-plan.prose.md 2.7 KB
- examples/auto-pocock/src/implement-tdd.prose.md 2.1 KB
- examples/auto-pocock/src/produce-issues.prose.md 1.2 KB
- examples/auto-pocock/src/produce-prd.prose.md 1.3 KB
- examples/auto-pocock/src/review-and-commit.prose.md 1.7 KB
- examples/auto-pocock/src/triage-and-pick.prose.md 1.6 KB
- examples/auto-pocock/src/verify-slice.prose.md 1.3 KB
- examples/basic-unit-suite/.gitignore 59 B
- examples/basic-unit-suite/README.md 4.8 KB
- examples/basic-unit-suite/src/alert-projection.prose.md 1.6 KB
- examples/basic-unit-suite/src/alert-state.prose.md 1.4 KB
- examples/basic-unit-suite/src/count-summary.prose.md 1.5 KB
- examples/basic-unit-suite/src/count-trend.prose.md 1.6 KB
- examples/basic-unit-suite/src/counter-events.prose.md 2.4 KB
- examples/basic-unit-suite/src/executive-snapshot.prose.md 1.6 KB
- examples/basic-unit-suite/src/format-alert-copy.prose.md 857 B
- examples/basic-unit-suite/src/raw-event-auditor.prose.md 1.1 KB
- examples/competitor-activity/.gitignore 133 B
- examples/competitor-activity/deps/.gitkeep 0 B
- examples/competitor-activity/prose.lock 38 B
- examples/competitor-activity/README.md 2.3 KB
- examples/competitor-activity/runs/.gitkeep 0 B
- examples/competitor-activity/src/competitor-activity-monitor.prose.md 4.0 KB
- examples/competitor-activity/state/.gitkeep 0 B
- examples/compliance-evidence-tracker/.gitignore 133 B
- examples/compliance-evidence-tracker/deps/.gitkeep 1 B
- examples/compliance-evidence-tracker/dist/.gitkeep 1 B
- examples/compliance-evidence-tracker/prose.lock 38 B
- examples/compliance-evidence-tracker/README.md 1.0 KB
- examples/compliance-evidence-tracker/runs/.gitkeep 1 B
- examples/compliance-evidence-tracker/src/collect-control-scope.prose.md 1.4 KB
- examples/compliance-evidence-tracker/src/compliance-evidence-current.prose.md 2.9 KB
- examples/compliance-evidence-tracker/src/evidence-review-events.prose.md 879 B
- examples/compliance-evidence-tracker/src/inspect-evidence.prose.md 1.5 KB
- examples/compliance-evidence-tracker/src/prepare-gap-brief.prose.md 1.3 KB
- examples/compliance-evidence-tracker/state/.gitkeep 1 B
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 · 413 lines · 133 tokens per session scan A 28696d9a8c1c
open-prose is a skill published in the GitHub repository openprose/prose (1,690 stars, last pushed 2d ago), licensed MIT. It adds 133 tokens to every session and 6,767 once invoked, about $0.0007 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…