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/implement-a-ticket/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/implement-a-ticket)<a href="https://agentmods.dev/skills/loerei/chronicle-mcp/implement-a-ticket"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/implement-a-ticket.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.00019 | $0.00959 |
| Opus 5 | $0.00010 | $0.00479 |
| Sonnet 5 | $0.00004 | $0.00192 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
implement-a-ticket 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 7d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement a Ticket
Execute mature, well-specified tickets directly from their acceptance criteria without recreating redundant implementation plans.
Directives
- Zero-Plan Mandate (No Re-planning): NEVER generate a new
implementation_plan.mdwhen a ticket already contains an explicit Acceptance Criteria checklist. The ticket's checklist IS the execution plan. - Context Pre-fetch: Run
node <skill-dir>/scripts/fetch-ticket.js <ticket-id-or-url>to download both the ticket and its parent PRD to.scratch/tickets/. - Targeted Seam Exploration: Inspect only the codebase seams and tests relevant to the current ticket before execution.
- Single-Step Progression: Mark progress directly on the ticket criteria:
[ ]->[/](max 1 active) ->[x]. - Empirical Verification: Run test commands (
npm test, build checks) to prove each acceptance criterion passes before marking[x]. - Atomic Close & Handoff:
- Commit changes referencing the ticket (e.g.
feat(scope): title (closes #<id>)). - Run
node <skill-dir>/scripts/close-ticket.js <ticket-id>on completion. - If next unblocked ticket exists: ask
"Do you want me to read Ticket <N> and implement?". - If all tickets in PRD are done: close parent PRD and output delivery summary.
- Commit changes referencing the ticket (e.g.
Workflow
flowchart TD
Start["Ticket URL / Issue ID"] --> Fetch["1. Run fetch-ticket.js (Pulls Ticket + Parent PRD)"]
Fetch --> Inspect["2. Inspect relevant codebase seams & tests"]
Inspect --> Confirm{"3. Report summary & ask: Implement?"}
Confirm -->|"User Approves / T3"| Loop["4. Execute Acceptance Criteria [ ] -> [/] -> [x] (TDD)"]
Confirm -->|"Clarifications / No"| Stop["Address feedback"]
Loop --> Verify{"All criteria [x] and tests pass?"}
Verify -->|"No"| Fix["Fix & re-run tests"] --> Loop
Verify -->|"Yes"| CommitClose["5. Commit, push & run close-ticket.js"]
CommitClose --> NextCheck{"Next unblocked ticket in PRD?"}
NextCheck -->|"Yes"| AskNext["Ask: Do you want me to read Ticket N and implement?"]
NextCheck -->|"No (All Done)"| ClosePRD["Close Parent PRD & Output Final Report"]
What ships with it
2 files 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.
- 7d ago First seen · 82 lines · 19 tokens per session scan A 2c69c8b851d7
implement-a-ticket is a skill published in the GitHub repository loerei/chronicle-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 959 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-08-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.