chronicle-mcp: Skill for Claude Code

.agents/skills/implement-with-subagents/SKILL.md

implement-with-subagents is a skill for Claude Code, Codex from loerei/chronicle-mcp. It costs 44 tokens per session (1,170 once invoked), scanned A, original, MIT.

A coordination method for carrying out several tickets or plan steps with separate coding agents. Each agent reads the actual specification file, while the coordinator manages order, Git instructions, testing, and context checks.

In plain words
What is it for?
Use it to dispatch PRD tickets or implementation steps one at a time, monitor agent context health, and require the relevant tests or checks after each step.
Why use it?
It prevents requirements from being lost or distorted when passed through a coordinator. Sequential execution also reduces branch conflicts and keeps each change separately reviewable.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; installed under .agents/ (shared by several agents).

This is loerei/chronicle-mcp's own configuration. It tells Claude Code and Codex how to work on chronicle-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything chronicle-mcp configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/loerei/chronicle-mcp/main/.agents/skills/implement-with-subagents/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/loerei/chronicle-mcp

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for implement-with-subagents

README.md
[![agentmods](https://agentmods.dev/badge/skills/loerei/chronicle-mcp/implement-with-subagents/github.svg)](https://agentmods.dev/skills/loerei/chronicle-mcp/implement-with-subagents)
Your own site
<a href="https://agentmods.dev/skills/loerei/chronicle-mcp/implement-with-subagents"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/implement-with-subagents/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.

agentmods 80×15 button for implement-with-subagents

Your own site · 80×15
<a href="https://agentmods.dev/skills/loerei/chronicle-mcp/implement-with-subagents"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/implement-with-subagents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,170 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.01170
Opus 5.5 $0.00018 $0.00468
Sonnet 5.5 $0.00009 $0.00234
Haiku 4.5 $0.00004 $0.00117

Measured 1mo ago against content hash 78d0b2ce7e75, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

implement-with-subagents 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.

.agents/skills/implement-with-subagents/SKILL.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implement With Subagents

Orchestrate multi-ticket or multi-step execution using sequential subagents, empirical context monitoring via chronicle, and strict separation of specs from orchestrator prompts.

Core Principles

  1. Zero Specs in Prompt (No Prompt Telephone Game):

    • The orchestrator prompt MUST NOT summarize, paraphrase, or re-explain requirements or acceptance criteria.
    • The prompt contains ONLY:
      • Target Ticket / Plan / Spec artifact path.
      • Git operational instructions (target branch, conventional commit template, issue closing directive closes #XX).
      • Tool and verification directives (e.g., test commands, linters).
    • The subagent MUST read the artifact file directly from disk.
  2. Sequential Ticket Execution:

    • Dispatch one ticket at a time to ensure atomic commits, clean git history, and conflict-free testing.
  3. Data-Driven Context Lifecycle Management:

    • Before assigning the next ticket to an existing subagent, inspect its context health using chronicle MCP tool get_session_benchmarks.
    • Never guess whether a subagent is degraded or truncated.

Workflow Decision Tree

flowchart TD
    Start["Ticket Ready to Dispatch"] --> HasSubagent{"Active Subagent Exists?"}
    
    HasSubagent -->|"No"| SpawnNew["invoke_subagent (Fresh Context)<br/>• Model: inherit<br/>• Role: Ticket Implementer"]
    
    HasSubagent -->|"Yes"| QueryBench["Call chronicle: get_session_benchmarks<br/>for subagent sessionId"]
    
    QueryBench --> EvaluateHealth{"Evaluate Context Health:<br/>• Checkpoint Count == 1 (Truncation count == 0)?<br/>• Curr. Context < 90,000 tokens?"}
    
    EvaluateHealth -->|"Healthy (Pass)"| ReuseSubagent["send_message (Continue Subagent)<br/>Pass next Ticket path + Git mandate"]
    EvaluateHealth -->|"Degraded / Truncated (Fail)"| SpawnNew
    
    SpawnNew --> WaitSubagent["Subagent reads Ticket file directly<br/>Executes TDD & implementation"]
    ReuseSubagent --> WaitSubagent
    
    WaitSubagent --> SubagentDone["Subagent Reports:<br/>• Modified files<br/>• Test & build output<br/>• Commit hash"]
    
    SubagentDone --> VerifyCommit["Orchestrator verifies test status & git log"]
    VerifyCommit --> MoreTickets{"More Tickets in Queue?"}
    MoreTickets -->|"Yes"| HasSubagent
    MoreTickets -->|"No"| Finalize["All Tickets Implemented → Final Quality Gate"]

Read the full file on GitHub · 110 lines

Changes

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.

  1. 1mo ago First seen · 110 lines · 44 tokens per session scan A 78d0b2ce7e75

Subscribe to this mod's changes

implement-with-subagents is a skill published in the GitHub repository loerei/chronicle-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 1,170 once invoked, about $0.0002 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-05.