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 eric-tramel/moraine --skill moraine-author-prgit clone --depth 1 https://github.com/eric-tramel/moraineWrote 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/eric-tramel/moraine/moraine-author-pr)<a href="https://agentmods.dev/skills/eric-tramel/moraine/moraine-author-pr"><img src="https://agentmods.dev/badge/skills/eric-tramel/moraine/moraine-author-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/eric-tramel/moraine/moraine-author-pr"><img src="https://agentmods.dev/badge/skills/eric-tramel/moraine/moraine-author-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.00079 | $0.01486 |
| Opus 5 | $0.00039 | $0.00743 |
| Sonnet 5 | $0.00016 | $0.00297 |
| Haiku 4.5 | $0.00008 | $0.00149 |
Grade A, and why
moraine-author-pr scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
For user-facing features, demonstrate the feature in the PR description. Use the most natural form for the change: CLI commands, config snippets, API calls, screenshots, curl examples, or monitor UI steps. How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Moraine Author PR
Overview
The goal is to create the PR on GitHub, not just draft title and body text in chat. The skill is complete when the PR exists on GitHub and you return its URL.
Always create a ready-for-review PR. Never create a GitHub Draft PR, never pass --draft, never set draft: true, and never emit an isDraft=true PR directive. If the branch is not ready for reviewer attention, stop and explain what remains instead of opening a Draft PR.
Write PR titles and descriptions that are reviewable, evidence-backed, and consistent across agents. Default bodies use Description, Usage, Changelog, and Validation sections. Base the summary on all commits in the branch, not only the latest one.
If the branch is not ready — uncommitted work, failing tests the user expects fixed first, or the user asked only to revise an existing PR description — say what is blocking creation and what remains. Do not pretend a PR was opened.
Title Rules
Use a concise imperative title. Prefer the repository's Conventional-Commit-like style:
feat(monitor): add token trend filters
fix(ingest): preserve cursor sqlite session ids
docs: document agent contributor workflows
chore: tighten sandbox cleanup handling
Do not include AI attribution in the title or body. Do not add generated-by footers, co-author trailers for agents, or notes that the PR was written by an AI tool.
Body Shape
Default to these sections:
## Description
**What.** [One sentence description].
**Why.** [One sentence description].
[Multi-paragraph description]
## Usage
[How users or developers will see this change]
## Changelog
- ...
## Validation
[Narrative description of how this was validated]
Keep sections short when the PR is small. Add focused extra sections only when useful, such as ## Bug Evidence, ## Performance, ## Operational Impact, or ## References.
Description
Open with bold one-line What. and Why. summaries, then expand in prose, bullets, or examples as needed.
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.
- 11d ago First seen · 215 lines · 79 tokens per session scan A 445f115b6381
moraine-author-pr is a skill published in the GitHub repository eric-tramel/moraine (117 stars, last pushed 25d ago), licensed Apache-2.0. It adds 79 tokens to every session and 1,486 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
block-no-verify-hook
Configure a PreToolUse hook to prevent AI agents from skipping git pre-commit hooks with --no-verify and other bypass flags. Use when setting up Claude Code projects that enforce commit quality gates.
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent - run one issue/PR pipeline on one repository as a supervised fleet. Auto-pick items, preflight every candidate to one deterministic claim verdict, stand up one worker session per item in a dedicated folder, probe them each cycle with one script call…
release-notes
Create release notes for a new version tag. Gathers all commits, PRs, issues fixed, and breaking changes since a previous release. Creates the release notes markdown file, tags the repo, and pushes. Asks the user to confirm the base version to diff against.