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 skills add markmhendrickson/neotoma --skill create_prgit clone --depth 1 https://github.com/markmhendrickson/neotomaWrote 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/markmhendrickson/neotoma/create_pr)<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/create_pr"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/create_pr/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/markmhendrickson/neotoma/create_pr"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/create_pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00098 | $0.03363 |
| Opus 5.5 | $0.00039 | $0.01345 |
| Sonnet 5.5 | $0.00020 | $0.00673 |
| Haiku 4.5 | $0.00010 | $0.00336 |
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 1mo 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/create_pr — Standardized PR creation
When to invoke
- User says
/create_pror asks to open a PR. - Another skill (
/process_issues,/process_prs,/release,/fix_feature_bug) reaches the point of opening a PR. Call this skill rather than inlininggh pr create. - A worktree has a committed branch ready for review and no PR exists yet.
Do not invoke when amending an existing PR description — use gh pr edit directly with the same body conventions below.
Inputs
The caller (or the user) should provide, or this skill should infer:
- Branch — current branch (
git branch --show-current); if it equals the configured main branch, stop and ask. - Base branch — usually
main; for release work, the RC branch. - Linked issue(s) — GitHub issue number(s) the PR closes or refers to.
- Source plan / spec — Neotoma
planentity_id ordocs/path, if any. - Change classification — bug fix / feature / refactor / docs / release. Drives commit-style prefix in the title.
- Functional surface touched — CLI command/flag, MCP tool, HTTP endpoint, observable event, schema field, runtime knob, integration. Drives the docs-coverage check below.
Functional change documentation (mandatory for functional changes)
Every PR that changes user-observable behavior MUST ship thorough markdown documentation under docs/, and MUST surface it via the docs server (src/services/docs/) and the docs site (docs/site/pages/ via docs/site/site_doc_manifest.yaml). A PR that adds, removes, or changes any of the following counts as functional:
- A CLI command, subcommand, flag, env var, or output format
- An MCP tool name, parameter, or response shape
- An HTTP endpoint, request/response field, or error envelope field
- An entity_type schema field, relationship type, or canonical-name rule
- An observable event payload, metric name, or log structure
- A user-visible runtime config knob (timeout, header policy, allow-list)
- An integration/provider added or removed
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.
- 1mo ago First seen · 242 lines · 98 tokens per session scan A d6da21234e4d
create_pr is a skill published in the GitHub repository markmhendrickson/neotoma (34 stars, last pushed 2d ago), licensed MIT. It adds 98 tokens to every session and 3,363 once invoked, about $0.0004 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-30.
Other skills, from other repositories
aura-integration
Automatically captures Gemini CLI intent and writes it to .gemini.intent whenever code changes are made. Use this skill when making any modifications to the codebase so that the local Aura Semantic Version Control system can track the AI's reasoning.
cratis-commits-and-pull-requests
Prepare coherent commits and release-note pull requests with the right release-intent label. Use when writing a commit message, staging commits, pushing, creating or editing a PR description, choosing major/minor/patch/no-release, or checking issue references in release notes. Not for assembling release candidates…
cratis-orchestration-merge-gates
Decide when an assembled candidate may merge during multi-lane work, using tier names, GitHub state for serial merge turns, a stale-head check, the review budget and an unattended no-prompt contract. Use when naming the gate tier for a lane, deciding whether it is this pull request's turn to merge, checking that a…
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.