Borrowing it
Nothing to install: this file belongs to loerei/chronicle-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/loerei/chronicle-mcp/main/.agents/skills/write-pr/SKILL.mdgit clone --depth 1 https://github.com/loerei/chronicle-mcpWrote 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/loerei/chronicle-mcp/write-pr)<a href="https://agentmods.dev/skills/loerei/chronicle-mcp/write-pr"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/write-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.1 | $0.00020 | $0.00453 |
| Opus 5 | $0.00010 | $0.00227 |
| Sonnet 5 | $0.00004 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
write-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 3d 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.
What it actually says
Write PR
Format and synchronize GitHub Pull Request descriptions using Conventional Commits and plain English.
Directives
- Title Format: MUST follow Conventional Commits:
<type>(<scope>): <short description>(e.g.,feat(cli): add short alias flags). - Session History Retrieval: When summarizing multi-turn sessions, MUST retrieve context via
chronicle-mcp(get_session_detailswithconversationStepsOnly: true). NEVER read raw SQLite or jsonl transcripts. - No Fluff: State factual code changes; NEVER use marketing adjectives (
robust,seamless,powerful).
| Bad (Marketing Fluff) | Good (Plain English) |
|---|---|
Leverages robust engine to seamlessly process input |
Parses CLI arguments using a key-value dictionary |
Significantly elevates velocity and eliminates friction |
Adds CLI aliases (-h, -d) for common commands |
Engineered fail-safe mechanisms against crash hazards |
Catches null errors and returns default config |
PR Template
## Summary
<Concise overview of what was changed>
---
## Why
- <Problem or friction point solved>
- <Business or technical rationale>
---
## Implementation Details
### <Component / Area>
- <Concrete technical modification>
- <Module behavior change>
---
## Files Changed
- `<file-path>`: <Brief change summary, mark `[NEW]` for additions>
Workflow
- Inspect Diffs & History: Check
git status,git diff, and retrieve session steps viachronicle-mcp. - Draft PR: Fill PR Template following Directives.
- Publish / Update:
- Create PR: Call
github:create_pull_request(orgh pr create). - Sync Drift: If subsequent commits modify scope, update PR body via
github:update_issue(orgh pr edit).
- Create PR: Call
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.
- 3d ago First seen · 59 lines · 20 tokens per session scan A 61bf031ab524
write-pr is a skill published in the GitHub repository loerei/chronicle-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 453 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-09-03.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…