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 AcKeskin/contexture --skill rulesgit 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/rules)<a href="https://agentmods.dev/skills/ackeskin/contexture/rules"><img src="https://agentmods.dev/badge/skills/ackeskin/contexture/rules/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/ackeskin/contexture/rules"><img src="https://agentmods.dev/badge/skills/ackeskin/contexture/rules.svg" alt="Reviewed on agentmods" width="80" 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.00087 | $0.00970 |
| Opus 5 | $0.00044 | $0.00485 |
| Sonnet 5 | $0.00017 | $0.00194 |
| Haiku 4.5 | $0.00009 | $0.00097 |
Grade A, and why
rules 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rules
Front door for the architectural-rule overlay system. Manages the user/company/project tiers that layer over the shipped architectural-rules/ tree. See docs/architectural-rules-overlay.md for the model.
Mode A only. Every mutating command previews the before→after effect on the effective corpus and waits for explicit confirmation before writing. Never auto-fires.
Tier directories
- shipped:
~/.claude/architectural-rules/(read-only here — never edit through this skill) - company:
~/.claude/architectural-rules-company/ - user:
~/.claude/architectural-rules-local/ - project:
<project>/.claude/rules/
Manifests: ~/.claude/architectural-rules.config.yaml (user), <project>/.claude/rules.config.yaml (project).
Subcommands
/rules list
Run the resolver (see docs/architectural-rules-overlay.md § Resolution). Show the effective corpus grouped by winning tier. Annotate only non-default rules: overridden, patched, disabled, or locked-and-diverged. Plain shipped rules show name + scope only.
/rules where <key>
The debug command. For one <scope>/<name> key, list every tier that defines it, which wins, and why (override / patch deltas / disable / lock). Show orphaned patch anchors if any.
/rules disable <key> [--project | --session]
- Resolve the key; show exactly which rule(s) vanish from the effective corpus.
- Default scope = global (user manifest
disabled:).--project→ project manifest.--session→ ephemeral, in-context note only, nothing written. - If the target carries
locked: true, require explicit confirmation naming the lock; on confirm, append adivergences:entry to the project manifest. - Preview → confirm → write.
/rules enable <key>
Remove the key from whichever manifest disabled: set holds it (project checked before user). Preview → confirm → write.
/rules edit <key> [--editor]
- Resolve the current winning tier for the key.
- Ask: whole-file override or field patch?
- whole-file → create
~/.claude/architectural-rules-local/<key>.mdseeded with the resolved lower-tier body (a real baseline, not blank). Setorigin: user. - field patch → create the same path with
override: <key>,mode: patch, and emptyremove/replace/addsections to fill in.
- whole-file → create
- Conversational by default: load the body into the chat; the user describes the change; apply via Edit with propose-confirm.
--editorinstead opens the file in$EDITORfor raw hand-editing. - If the target is
locked: true, confirm + write a divergence entry (as indisable). - Show the resulting effective rule (post-resolution) so the user sees the merged outcome.
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 · 59 lines · 87 tokens per session scan A b90a28c2981e
rules is a skill published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 1mo ago), licensed MIT. It adds 87 tokens to every session and 970 once invoked, about $0.0004 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.
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.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
ios-development
Comprehensive guide for building native Apple platform applications.