What is write-a-principle?

A document-writing workflow for creating an architecture principle from a standard template, such as a rule about data ownership or governance. It writes the result into the private lab repository's `principles/` folder.

Use it to draft, scaffold, or add a principle from a private lab repository, typically with the toolkit mounted as a submodule.

It gives architecture principles a consistent structure and keeps private decision guidance separate from the public toolkit repository.

write-a-principle — Skill for Claude Code and Codex by Future-CX

Install

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.

Any agent

npx skills add Future-CX/AI-Architecture-Toolkit --skill write-a-principle

Clone the repo

git clone --depth 1 https://github.com/Future-CX/AI-Architecture-Toolkit

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/future-cx/ai-architecture-toolkit/write-a-principle/github.svg)](https://agentmods.dev/skills/future-cx/ai-architecture-toolkit/write-a-principle)

Your own site

<a href="https://agentmods.dev/skills/future-cx/ai-architecture-toolkit/write-a-principle"><img src="https://agentmods.dev/badge/skills/future-cx/ai-architecture-toolkit/write-a-principle/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/future-cx/ai-architecture-toolkit/write-a-principle"><img src="https://agentmods.dev/badge/skills/future-cx/ai-architecture-toolkit/write-a-principle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,253 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.

Model	Per session	Once invoked
Fable 5.1	$0.00058	$0.01253
Opus 5.5	$0.00023	$0.00501
Sonnet 5.5	$0.00012	$0.00251
Haiku 4.5	$0.00006	$0.00125

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

Security

Grade A, and why

write-a-principle 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 2mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/write-principle.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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-a-principle/SKILL.md · 141 lines

How it starts

The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Write A Principle

Quick Start

Always run this skill from a private lab repository where this toolkit is mounted as a submodule, typically toolkit/. Write generated principle documents under the private lab repository's root principles/ folder using the preset template in toolkit/skills/write-a-principle/templates/principle-template.md.

Do not run this skill from the public toolkit repository for generated output. Do not write generated principle files under toolkit/principles/. Run the command from the private lab root, or pass --output-root <private-lab-root>, so output goes to <private-lab-root>/principles/.

If running from a different working directory, explicitly target the private lab root:

python3 toolkit/skills/write-a-principle/scripts/write-principle.py "Data Architecture Principles" \
  --category-code DATA \
  --intent "Define durable data architecture principles for ownership, quality, governance, and integration." \
  --principle "Data ownership must be explicit and aligned to business domains" \
  --principle-description "Every important data object must have a named business owner and stewardship model" \
  --principle-rationale "Ownership makes data quality, access, lifecycle, and change decisions accountable" \
  --principle-consequence "Teams must identify ownership before introducing or changing critical data flows" \
  --principle-do "Name the owning domain or team for each critical data object" \
  --principle-dont "Treat shared data as ownerless platform inventory" \
  --principle "Critical data must have defined quality expectations and stewardship" \
  --usage "Use these principles when designing data platforms, integrations, analytics products, and governance processes." \
  --output-root <private-lab-root>

Run from the private lab root, this creates principles/data-architecture-principles.md beside toolkit/.

Each generated principle is also added to principles/_principles-list.md using a markdown table with name, description, and last_updated columns. Create _principles-list.md when it does not exist. Keep rows sorted alphabetically by principle name.

Read the full file on GitHub · 141 lines

Files

What ships with it

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

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.

2mo ago First seen · 141 lines · 58 tokens per session scan A 8d77e7e47ded

Subscribe to this mod's changes

write-a-principle is a skill published in the GitHub repository Future-CX/AI-Architecture-Toolkit (8 stars, last pushed 18d ago), licensed MIT. It adds 58 tokens to every session and 1,253 once invoked, about $0.0002 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

write-a-principle next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
write-a-principleFuture-CX/AI-Architecture-Toolkit	Skill	8	18d ago	MIT	A	58	Claude Code, Codex
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	314k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code