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/ackeskin/contexture/extract-conventionsnpx skills add AcKeskin/contexture --skill extract-conventionsgit clone --depth 1 https://github.com/AcKeskin/contextureWrote 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/ackeskin/contexture/extract-conventions)<a href="https://agentmods.dev/skills/ackeskin/contexture/extract-conventions"><img src="https://agentmods.dev/badge/skills/ackeskin/contexture/extract-conventions.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.00056 | $0.03444 |
| Opus 5 | $0.00028 | $0.01722 |
| Sonnet 5 | $0.00011 | $0.00689 |
| Haiku 4.5 | $0.00006 | $0.00344 |
Grade A, and why
extract-conventions 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 2d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
extract-conventions
The convention-extraction organ. Auto-populates the project rule tier. Gates on the rule-prime hook for its output to be load-bearing — without the hook priming the extracted file, it is an inert surface. Feeds naming-and-comments, whose audit cites the project-tier conventions this writes.
Extract observes a scope and makes its implicit, tacit conventions explicit — a durable artefact the rule-prime hook primes and /review audits, rather than stateless per-run re-inference that is drift-prone and points a reviewer at nothing.
When to run
- User types
/extract-conventions <scope>(or with no arg → prompt for scope). - Natural language: "capture this module's conventions", "extract our house style", "codify how this codebase names things".
- Do not auto-fire. Mode A, user-invoked only. Extracting and writing a project-tier rule is a deliberate act, never a session side effect. No hook, no session-start trigger.
Inputs
-
Scope argument — a directory (
src/auth/), a module, or a language (csharp). With no arg, prompt:What scope should I extract conventions from? A directory (
src/auth/), a module, or a language (csharp). -
Working directory —
$CLAUDE_PROJECT_DIRorcwd. Anchors the write target (<project>/.claude/rules/...) and the rule-overlay resolution. -
Per-category accept/edit/reject decisions — collected at the confirm gate (§4). Collaborator principle — never auto-write.
Procedure
1. Resolve scope and sample
Resolve the scope argument to a concrete file set:
| Form | Resolution |
|---|---|
directory (src/auth/) |
every source file under it (recursive), respecting .gitignore |
language (csharp) |
every file of that language across the project (by extension) |
| module name | the directory matching it; if ambiguous, list candidates and ask |
Consume the scope-resolution resolver where shipped for the boundary/granularity model; degrade to language-level when it isn't present. Do not invent a competing granularity model.
What ships with it
1 file 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.
- 2d ago First seen · 198 lines · 56 tokens per session scan A 68e1db3ccef2
extract-conventions is a skill published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 3,444 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-09-03.
Other skills, from other repositories
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
email-systems
Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability.
ios-development
Comprehensive guide for building native Apple platform applications.
ai-policy-generator
AI governance policy creation for nonprofits and enterprises with frameworks, risk assessment, ethical guidelines, and compliance templates. Use when drafting AI usage policies, responsible AI frameworks, or organizational AI governance documents.
battle-card-builder
Competitive battle card creation for sales teams combining competitive intelligence, sales enablement, and document formatting. Use when building battle cards, competitive analysis decks, or win/loss analysis materials.