chronicle-mcp: Skill for Claude Code

.agents/skills/write-a-request/SKILL.md

write-a-request is a skill for Claude Code, Codex from loerei/chronicle-mcp. It costs 19 tokens per session (333 once invoked), scanned A, original, MIT.

A guide for drafting feature requests, change proposals, and RFCs, which are documents used to discuss proposed technical changes.

In plain words
What is it for?
Use it to describe a bottleneck, propose a behavioral or interface change, and explain its practical value.
Why use it?
It keeps proposals tied to observed problems and avoids unsupported claims about how the system should be built internally.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: 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/write-a-request/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 write-a-request

README.md
[![agentmods](https://agentmods.dev/badge/skills/loerei/chronicle-mcp/write-a-request.svg)](https://agentmods.dev/skills/loerei/chronicle-mcp/write-a-request)
Your own site
<a href="https://agentmods.dev/skills/loerei/chronicle-mcp/write-a-request"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/write-a-request.svg" alt="Measured on agentmods" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 333 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.00019 $0.00333
Opus 5 $0.00010 $0.00167
Sonnet 5 $0.00004 $0.00067
Haiku 4.5 $0.00002 $0.00033

Measured 3d ago against content hash 4f9139bf4436, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

write-a-request 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.

.agents/skills/write-a-request/SKILL.md · 48 lines

What it actually says

Write a Request

Draft idea-level proposals, behavioral change requests, and policy enhancements in REQUEST.md (or request_<topic>.md).

Directives

  1. Zero Speculation: Propose at the behavioral or interface level (what/how it looks); NEVER dictate internal algorithms or guessed architecture.
  2. Concrete Grounding: MUST anchor the problem in an observed bottleneck or real example; no hypothetical generalities.
  3. No Fluff Rationale: State direct technical value and saved friction without marketing hype.

Template (REQUEST.md)

# Request: [Short Descriptive Summary]

**Target**: `<tool / document / repository>`  
**Type**: `[Feature / Policy / Enhancement]`  
**Date**: YYYY-MM-DD  

---

## 1. Problem (What)
- Concrete friction point, missing option, or workflow bottleneck. Include observed example.

## 2. Proposed Idea (Do What)
- Desired behavioral, parameter, or interface change at conceptual level.
- Do NOT dictate internal implementation mechanics.

## 3. Rationale (Why)
- Direct operational value and friction eliminated.

Workflow

  1. Identify the target entity and exact friction point.
  2. Formulate behavioral proposal following Directives.
  3. Write artifact to REQUEST.md (or <appDataDir>/brain/<convo-id>/request_<topic>.md).
  4. Present file link and brief summary to user.
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. 3d ago First seen · 48 lines · 19 tokens per session scan A 4f9139bf4436

Subscribe to this mod's changes

write-a-request is a skill published in the GitHub repository loerei/chronicle-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 333 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens