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 commands/monarch-initiative/dismech/create-prgit clone --depth 1 https://github.com/monarch-initiative/dismechWrote 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/monarch-initiative/dismech/create-pr)<a href="https://agentmods.dev/commands/monarch-initiative/dismech/create-pr"><img src="https://agentmods.dev/badge/commands/monarch-initiative/dismech/create-pr.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.00010 | $0.00637 |
| Opus 5 | $0.00005 | $0.00318 |
| Sonnet 5 | $0.00002 | $0.00127 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
create-pr 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a pull request from work that you have done. Typically this is a new disease, but in some cases it may be QC improvements or enhancements to existing diseases.
Use the github-communication skill when writing the PR body: lead with the
finding in plain language, pitch the opening at the audience the PR is really
for, and keep the jargon for further down. Remember to say what you
intentionally did NOT do, and why.
ALWAYS make sure your work has been validated (see justfile for targets). Best efforts should be made to reach high compliance with guidelines, but we can always iterate
Generally a PR should be about a single disease. However, in some cases it makes sense to batch changes together. Use judgment.
What SHOULD be included in a PR
- the yaml file (kb/disorders/DISORDER.yaml)
- the deep research results for that disorder (if a new disorder is created)
- any publications added to the cache
- term cache changes
- a history record under
history/describing this curation session (see below)
Record a history entry (required for KB changes)
Any PR that creates or edits a KB entry (kb/disorders/, kb/modules/, or
kb/comorbidities/) should also add an append-only history record so curation
provenance keeps pace with content. CI posts an advisory warning when a KB entry
changes without one.
Scaffold it with the helper (never hand-write the path/timestamp):
just new-history --kind disorder --slug DISORDER \
--event CREATE --outcome changed \
--summary "Create: DISORDER" \
--agent-tool claude-code --model <model-id> \
--sections phenotypes,pathophysiology,evidence,treatments \
--pr <PR_NUMBER> --issue <ISSUE_NUMBER> \
--details "One-paragraph summary of what was curated and how it was validated."
Use --event EDIT for enhancements to an existing entry, --event REVIEW for a
review, and --kind module/--kind comorbidity for those targets. Then edit the
emitted details if needed, validate, and stage it:
just validate-history <path-printed-by-new-history>
git add history/
See docs/history.md for the full format. The PR number may not exist yet when
you scaffold — either pass it after opening the PR, or add it to the record's
links.prs in a follow-up commit.
What should NOT be included
- derived browser files (e.g. app.js, HTML files); these are added later by a weekly job
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 · 64 lines · 10 tokens per session scan A eddd5cbbeb8e
create-pr is a command published in the GitHub repository monarch-initiative/dismech (56 stars, last pushed 4d ago), licensed BSD-3-Clause. It adds 10 tokens to every session and 637 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-08-30.
Other commands, from other repositories
README
Git workflow and quality assurance commands for the claude-skills repository.
tokenless-stats
Show Tokenless compression statistics.
execute
Interactive workflow for workspace isolation, pane-delegated implementation, testing, review, and cleanup.
fix-issue
!gh issue view $ARGUMENTS 2>/dev/null || echo "Could not fetch issue $ARGUMENTS".
cadence-handoff
Scaffold a SESSION handoff doc with machine facts pre-filled.
unity-optimize
Profile and optimize performance — uses MCP profiler for frame timing, memory, rendering stats. Identifies bottlenecks and applies fixes.