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/manage-custom-skills/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/manage-custom-skills)<a href="https://agentmods.dev/skills/loerei/chronicle-mcp/manage-custom-skills"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/manage-custom-skills/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/manage-custom-skills"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/manage-custom-skills.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.00030 | $0.00578 |
| Opus 5 | $0.00015 | $0.00289 |
| Sonnet 5 | $0.00006 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
manage-custom-skills 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 12d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Custom Skills
Author skills in the central myskills/ source catalog, then distribute them to project workspaces and IDE targets.
Workflow
flowchart TD
Start["Skill Request"] --> Source["1. Edit Source SKILL.md in myskills/<category>/<name>/"]
Source --> Distribute["2. Sync Workspaces: agents distribute"]
Distribute --> Audit["3. Sync Table 1 Policy: agents audit -a -p"]
Audit --> Git["4. Commit & Push myskills"]
Core Rules
- Source-First Mandate: ALWAYS edit skills directly in
<myskills-root>/<category>/<skill-name>/SKILL.md. NEVER edit project-local copies in.agents/skills/(they are overwritten on distribution unless frontmatter setslocal: true). - Lookup Tooling:
- Find source path:
agents info skill.<skill-name>(oragents wherefor root). - Read skill stdout:
agents read skill.<skill-name>.
- Find source path:
- Distribution: Run
agents distribute(oragents distribute -t .for current repo only) to sync changes to workspaces and IDE configs (~/.gemini,~/.claude,~/.cursor). - Policy Audit: Run
agents audit -a -pafter adding, renaming, or deleting skills to syncTable 1inAGENTS.md.
Categories & Frontmatter
| Category | Domain Scope |
|---|---|
design/ |
UI/UX, styling, frontend aesthetics, mobile/web comps |
engineering/ |
Architecture, TDD, debugging, domain modeling, refactoring |
quality/ |
Sonar remediation, code reviews, benchmark testing |
productivity/ |
Automation workflows, PRs, AI writing, issue triage |
personal/ |
Notes, writing drafts, Obsidian vault management |
---
name: <skill-name>
description: <Concrete capability>. Use when [specific triggers].
---
CLI Reference
| Command | Action |
|---|---|
agents distribute |
Sync all skills to all registered project workspaces and IDEs |
agents distribute -t <path> |
Sync skills to a specific project directory |
agents audit |
Check policy coverage without modifying files |
agents audit -a -p |
Add missing skills to Table 1 and prune deleted skills from AGENTS.md |
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.
- 12d ago First seen · 54 lines · 30 tokens per session scan A d22f06308efb
manage-custom-skills is a skill published in the GitHub repository loerei/chronicle-mcp (0 stars, last pushed 7d ago), licensed MIT. It adds 30 tokens to every session and 578 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…