agentmods.dev

write-convention

write-convention is a skill for Claude Code from cpliakas/claude-code-engineering-leaders. It costs 63 tokens per session (1,342 once invoked), scanned A, original, MIT.

A convention-writing router that sends a new coding convention to one of five areas: implementation, infrastructure, quality, user experience, or architecture. A convention is a documented rule for how a project should be built or maintained.

In plain words
What is it for?
Use it to author a convention with a domain flag or domain name, such as a rule about testing, deployment, interface design, or system structure. If no domain is given, it uses tactical implementation.
Why use it?
It keeps new rules associated with the right part of the project and provides a consistent way to choose that area.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is See the [Convention Ownership Matrix](../../README.md#convention-ownership-matrix).

not rated 4repo 1mo ago A scan 63 tokens original MIT archived

Good fit Use it to author a convention with a domain flag or domain name, such as a rule about testing, deployment, interface design, or system structure. If no domain is given, it uses tactical implementation.

Compare 6 skills from other repositories ↓
View source ↗ cpliakas/claude-code-engineering-leaders
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/cpliakas/claude-code-engineering-leaders
agentmods
npx agentmods add skills/cpliakas/claude-code-engineering-leaders/write-convention

Made for: Claude Code.

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-convention

README.md
[![agentmods](https://agentmods.dev/badge/skills/cpliakas/claude-code-engineering-leaders/write-convention/github.svg)](https://agentmods.dev/skills/cpliakas/claude-code-engineering-leaders/write-convention)
Your own site
<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/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.

agentmods 80×15 button for write-convention

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,342 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.00063 $0.01342
Opus 5.5 $0.00025 $0.00537
Sonnet 5.5 $0.00013 $0.00268
Haiku 4.5 $0.00006 $0.00134

Measured 1mo ago against content hash e93e7f969d2b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

skills/write-convention/SKILL.md · 190 lines

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:

  1. 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.

  2. Convention name — everything in $ARGUMENTS that 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-implementation
  • infrastructure
  • quality
  • ux
  • architecture

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:

Read the full file on GitHub · 190 lines

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. 1mo ago First seen · 190 lines · 63 tokens per session scan A e93e7f969d2b

Subscribe to this mod's changes

write-convention is a skill published in the GitHub repository cpliakas/claude-code-engineering-leaders (4 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 1,342 once invoked, about $0.0003 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-31.

Writing and docs
Related

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…

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

systematic-debugging

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

obra/superpowers · 21 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

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens