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/gitpublish-prd-and-tickets/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/gitpublish-prd-and-tickets)<a href="https://agentmods.dev/skills/loerei/chronicle-mcp/gitpublish-prd-and-tickets"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/gitpublish-prd-and-tickets/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/loerei/chronicle-mcp/gitpublish-prd-and-tickets"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/gitpublish-prd-and-tickets.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.00029 | $0.00976 |
| Opus 5 | $0.00015 | $0.00488 |
| Sonnet 5 | $0.00006 | $0.00195 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade A, and why
gitpublish-prd-and-tickets 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 6d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitPublish PRD and Tickets
Publish or synchronize a local PRD and its constituent ticket markdown files to GitHub Issues with parallel batch concurrency. Resolves semantic keys (01.1.1.1, 02.1), maps dependencies across both intra-PRD and cross-PRD references, updates parent PRD links, attaches standardized taxonomy labels, and handles in-place updates, splits, and deletions with zero duplicates.
Core Directives
- Source Purity & Zero Disk Mutation (SSOT Preservation):
- Local files under
docs/specs/(PRD.mdandtickets/*.md) MUST remain 100% pure semantic files and NEVER be modified on disk by the publish script. - All transformations (
01.1$\to$#138 (01.1), parent references) are compiled ephemerally in memory / OS tempdir exclusively for GitHub API upload. - Reviewers in
/conduct-deep-reviewing-loopcontinue to work with clean semantic keys without mutable GitHub issue IDs pollution.
- Local files under
- High-Performance Parallel Execution: Runs in-place ticket updates and non-dependent ticket creations concurrently using an internal worker pool (
--concurrency <N>, default: 6). - Batch Multi-Epic Synchronization: Supports
--allflag to discover, pre-scan, and synchronize all Epics underdocs/specs/in a single command. - Idempotent Reconciliation:
- Matching Key (
01.1$\to$01.1): Executes in-place update (gh issue edit) on the existing GitHub issue without creating duplicates. - New Key (Split child
01.1.1or added05.2): Creates a new issue (gh issue create). - Orphaned Key (Old
01.1removed or split): Automatically closes the stale remote issue with reason not planned and closing comment (gh issue close --reason "not planned" --comment "...").
- Matching Key (
- Topological Publishing: Publishes tickets in topological order so that prerequisite tickets receive GitHub issue IDs before dependent tickets.
- Standardized Taxonomy Auto-Labels:
- Parent PRD:
epic,epic-<num>(e.g.epic,epic-02) - Child Tickets:
ticket,epic-<num>(e.g.ticket,epic-02)
- Parent PRD:
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.
- 6d ago First seen · 65 lines · 29 tokens per session scan A 2030d68422db
gitpublish-prd-and-tickets is a skill published in the GitHub repository loerei/chronicle-mcp (0 stars, last pushed 6d ago), licensed MIT. It adds 29 tokens to every session and 976 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-05.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.