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-with-subagents/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-with-subagents)<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="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.00044 | $0.01170 |
| Opus 5 | $0.00022 | $0.00585 |
| Sonnet 5 | $0.00009 | $0.00234 |
| Haiku 4.5 | $0.00004 | $0.00117 |
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 2d 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 — 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
-
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.
-
Sequential Ticket Execution:
- Dispatch one ticket at a time to ensure atomic commits, clean git history, and conflict-free testing.
-
Data-Driven Context Lifecycle Management:
- Before assigning the next ticket to an existing subagent, inspect its context health using
chronicleMCP toolget_session_benchmarks. - Never guess whether a subagent is degraded or truncated.
- Before assigning the next ticket to an existing subagent, inspect its context health using
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"]
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.
- 2d ago First seen · 110 lines · 44 tokens per session scan A 78d0b2ce7e75
implement-with-subagents is a skill published in the GitHub repository loerei/chronicle-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 1,170 once invoked, about $0.0002 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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.