Borrowing it
Nothing to install: this file belongs to chirino/memory-service. 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/chirino/memory-service/main/.skills/enhancement-docs/SKILL.mdgit clone --depth 1 https://github.com/chirino/memory-serviceWrote 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/chirino/memory-service/enhancement-docs)<a href="https://agentmods.dev/skills/chirino/memory-service/enhancement-docs"><img src="https://agentmods.dev/badge/skills/chirino/memory-service/enhancement-docs/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/chirino/memory-service/enhancement-docs"><img src="https://agentmods.dev/badge/skills/chirino/memory-service/enhancement-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00027 | $0.01113 |
| Opus 5.5 | $0.00011 | $0.00445 |
| Sonnet 5.5 | $0.00005 | $0.00223 |
| Haiku 4.5 | $0.00003 | $0.00111 |
Grade A, and why
enhancement-docs 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enhancement Document Format
Enhancement docs use the naming convention NNN-kebab-case-title.md where NNN is zero-padded and sequential.
- New/proposed docs live in
docs/enhancements/. - Non-proposed docs move to
docs/enhancements/<status>/where status isimplemented,partial, orsuperseded.
Check the highest existing number before creating a new one (sort on file names, not paths, so the status subdirectories don't skew the order):
find docs/enhancements -name '[0-9]*.md' -exec basename {} \; | sort -n | tail -5
Some numbers are shared by two docs (for example 090, 091, and 116). Refer to those docs by file name, not number alone. The 4xx numbers are a separate range; pick the next number in the main sequence unless told otherwise.
Required Structure
Every enhancement doc must include:
1. YAML Front Matter
---
status: proposed
---
Valid statuses: proposed, implemented, partial, superseded.
When superseded, add:
---
status: superseded
superseded-by:
- implemented/NNN-replacement-name.md
---
2. Title & Status Line
# Enhancement NNN: Brief Descriptive Title
> **Status**: Proposed.
For implemented docs: > **Status**: Implemented.
For partial: > **Status**: Partial — see [NNN](../implemented/NNN-name.md) for continuation.
3. Core Sections
| Section | Required | Purpose |
|---|---|---|
| Summary | Yes | 1-2 sentence overview of the change |
| Motivation | Yes | Why this is needed — current problems, risks, use cases |
| Design | Yes | Technical approach — API changes, data model changes, code examples |
| Testing | Yes | Test strategy — Cucumber scenarios (gherkin), unit test patterns |
| Tasks | Yes | Checkbox list of work items: - [ ] task / - [x] done |
| Files to Modify | Yes | Markdown table of files and what changes in each |
| Verification | Yes | Exact commands to compile and run tests |
| Non-Goals | Optional | Explicitly out of scope items |
| Design Decisions | Optional | Rationale for key choices |
| Security Considerations | Optional | Risk mitigations if relevant |
| Open Questions | Optional | Unresolved items needing discussion |
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.
- 1mo ago Changed 7e48360db7f1
- 2mo ago First seen · 105 lines · 27 tokens per session scan A 10e88b1c90ef
enhancement-docs is a skill published in the GitHub repository chirino/memory-service (12 stars, last pushed yesterday), licensed Apache-2.0. It adds 27 tokens to every session and 1,113 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…