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 agentmods add skills/cpliakas/claude-code-engineering-leaders/write-conventionnpx skills add cpliakas/claude-code-engineering-leaders --skill write-conventiongit clone --depth 1 https://github.com/cpliakas/claude-code-engineering-leadersWrote 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/cpliakas/claude-code-engineering-leaders/write-convention)<a href="https://agentmods.dev/skills/cpliakas/claude-code-engineering-leaders/write-convention"><img src="https://agentmods.dev/badge/skills/cpliakas/claude-code-engineering-leaders/write-convention.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.00063 | $0.01342 |
| Opus 5 | $0.00032 | $0.00671 |
| Sonnet 5 | $0.00013 | $0.00268 |
| Haiku 4.5 | $0.00006 | $0.00134 |
Grade A, and why
write-convention 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 5d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Convention
Route convention authorship to the declared domain owner for the convention
described in $ARGUMENTS.
Step 1 — Parse Arguments
Extract two pieces of information from $ARGUMENTS:
-
Domain — accept either:
- Flag form:
--domain=<value>anywhere in the argument string. - Positional form: a bare word appearing before the convention name that
exactly matches one of the five valid domain strings
(
tactical-implementation,infrastructure,quality,ux,architecture). - If neither form is present, default to
tactical-implementation.
- Flag form:
-
Convention name — everything in
$ARGUMENTSthat is not the domain flag or the positional domain token.
If $ARGUMENTS is empty (no convention name), ask the user to provide a
convention name before proceeding.
Step 2 — Validate Domain
Check the extracted domain against the fixed vocabulary:
tactical-implementationinfrastructurequalityuxarchitecture
If the value is not one of these five strings, emit the following message:
"<value>"is not a recognized convention domain. Valid domains are:tactical-implementation,infrastructure,quality,ux,architecture.Which domain should this convention belong to?
Prompt the user for a valid domain. Do not proceed until a valid domain is supplied.
Step 3 — Resolve Owner Agent
Map the validated domain to its owner agent:
| Domain | Owner Agent |
|---|---|
tactical-implementation |
tech-lead |
infrastructure |
devops-lead |
quality |
qa-lead |
ux |
ux-strategist |
architecture |
chief-architect |
Step 4 — Read Conventions Directory Path
Read the Tech Lead's memory at
.claude/agent-memory/engineering-leaders-tech-lead/MEMORY.md.
Look for a Conventions Directory path (typically listed under a
## Conventions Directory section or ## Project File References section).
If no conventions directory path is configured, emit the following error and stop:
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.
- 5d ago First seen · 190 lines · 63 tokens per session scan A e93e7f969d2b
write-convention is a skill published in the GitHub repository cpliakas/claude-code-engineering-leaders (4 stars, last pushed 14d ago), licensed MIT. It adds 63 tokens to every session and 1,342 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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…
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…