Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ashermahonin/agentic-skills --skill service-implementationgit clone --depth 1 https://github.com/ashermahonin/agentic-skillsWrote 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/ashermahonin/agentic-skills/service-implementation)<a href="https://agentmods.dev/skills/ashermahonin/agentic-skills/service-implementation"><img src="https://agentmods.dev/badge/skills/ashermahonin/agentic-skills/service-implementation.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.00067 | $0.00583 |
| Opus 5 | $0.00034 | $0.00292 |
| Sonnet 5 | $0.00013 | $0.00117 |
| Haiku 4.5 | $0.00007 | $0.00058 |
Grade A, and why
service-implementation 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 6d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Service Implementation
Purpose
Change production code within an agreed boundary and leave enough evidence for another engineer to verify the result.
Change context
- Read the assigned task, requirements, architecture notes, and write scope.
- Read the failing test and implementation contract from
tdd-workflowwhen present. - Read the recommendation from
engineering-qualitywhen the route includes maintainability or refactoring work. - Inspect nearby code before choosing patterns.
- Confirm tests or validation commands before editing.
- Check for dirty files and avoid overwriting unrelated user changes.
Change method
- Reproduce the current behavior or failure before editing when the task permits it.
- Make the smallest coherent change that satisfies the acceptance criteria and failing test.
- Reuse local patterns and dependencies. Add an abstraction only when it protects a real boundary or removes proven duplication.
- Keep interface, data, migration, and backward-compatibility effects explicit.
- Add or adjust a boundary or failure test if the existing contract could pass an incorrect implementation.
- Run the narrow verification first, then the affected suite. Report any check that could not run and why.
- Update the canonical documentation, runbook, ADR, or project note when behavior or operating steps change.
Engineering constraints
- Apply
engineering-qualityto new production code and focused refactors. - Use current primary documentation before relying on external technology behavior. Context7 MCP is the preferred documentation source when available.
- Preserve dirty or unrelated files. Do not overwrite work that is outside the assigned scope.
- Obtain approval immediately before an irreversible, production-facing, costly, or security-sensitive action.
- Keep comments about hidden constraints and tradeoffs; let names and structure explain ordinary behavior.
Evidence
- Files and behavior changed
- Acceptance criteria satisfied
- Tests and validation commands with results
- Documentation or project memory updated
- Remaining risk, rollback, and deferred work
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 62 lines · 67 tokens per session scan A accbd16dc7c8
service-implementation is a skill published in the GitHub repository ashermahonin/agentic-skills (10 stars, last pushed 13d ago), licensed MIT. It adds 67 tokens to every session and 583 once invoked, about $0.0003 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…