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 0ryant/engineering-doctrine --skill method-record-classificationgit clone --depth 1 https://github.com/0ryant/engineering-doctrineWrote 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/0ryant/engineering-doctrine/method-record-classification)<a href="https://agentmods.dev/skills/0ryant/engineering-doctrine/method-record-classification"><img src="https://agentmods.dev/badge/skills/0ryant/engineering-doctrine/method-record-classification/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/0ryant/engineering-doctrine/method-record-classification"><img src="https://agentmods.dev/badge/skills/0ryant/engineering-doctrine/method-record-classification.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.00079 | $0.01094 |
| Opus 5.5 | $0.00032 | $0.00438 |
| Sonnet 5.5 | $0.00016 | $0.00219 |
| Haiku 4.5 | $0.00008 | $0.00109 |
Grade A, and why
method-record-classification 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Method-Record Classification Skill
Kind: change-lifecycle procedure Authority: advisory; the named human author owns the class asserted
Purpose
Discharge the disclosure duty in code-review-and-change-approval.md §6 the way ADR 0043 requires: a tool is never a co-author, and how the candidate was produced is recorded in a separately addressable, falsifiable field. The class vocabulary is defined in §6.1 of the pattern; this skill only makes an agent apply it before the candidate leaves its hands.
Instructions
Before you finalise a commit or change candidate:
1. Never write a non-human tool into an authorship field: Author, Co-Authored-By, Signed-off-by, or any successor that confers standing. The named human holds authorship, ownership, and accountability whole.
2. Classify the candidate honestly. generated: accepted substantially as produced, review was inspection. curated: produced under a declared, revision-pinned harness and ruleset, then materially revised by the named author. authored: written by the author; ordinary tool assistance does not change this.
3. Record the class with the revision-pinned harness and ruleset in a field that makes no authorship claim. Recommended trailer: Produced-With: harness=<id>@<rev>; doctrine=<id>@<rev>; class=<class>. An authored change MAY omit the record.
4. Claim curated only when both revisions are pinned and the material revision is visible in the diff. curated is falsifiable and is not a courtesy upgrade from generated.
5. The record is required in estate-governed and production paths and a strong default elsewhere. If the estate binds a different key, use it. If it binds an authorship field, refuse and flag the binding.
6. If you cannot determine the class, say so and leave the decision to the named author rather than guessing.
Run-Contract Use
What ships with it
1 file 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.
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 Changed · +1 lines 706b5abd32c6
- 1mo ago First seen · 95 lines · 79 tokens per session scan A 94255f9edc00
method-record-classification is a skill published in the GitHub repository 0ryant/engineering-doctrine (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 79 tokens to every session and 1,094 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-09-04.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
hero-diff-highlight
A dark code editor reveals a red deletion then a green addition with a soft pulse. Function: PR / code-change explainer.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.