CCBuddy: Skill for Codex

.agents/skills/architecture-governance/SKILL.md

architecture-governance is a skill for Codex from ccbud/CCBuddy. It costs 45 tokens per session (1,000 once invoked), scanned A, original, Apache-2.0.

A code-change planning and checking skill that applies a repository's architecture rules before implementation. Architecture rules describe which parts of a codebase may depend on one another and where behavior should live.

In plain words
What is it for?
Use it to create a focused design package, inspect related contracts and tests, update specifications, check changed files, and report violations against the existing baseline.
Why use it?
It helps prevent code from crossing module or layer boundaries unexpectedly and makes ownership, behavior, and migration decisions explicit before editing files.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is ccbud/CCBuddy's own configuration. It tells Codex how to work on CCBuddy itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything CCBuddy configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ccbud/CCBuddy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ccbud/CCBuddy/main/.agents/skills/architecture-governance/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ccbud/CCBuddy

Made for: 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.

agentmods badge for architecture-governance

README.md
[![agentmods](https://agentmods.dev/badge/skills/ccbud/ccbuddy/architecture-governance/github.svg)](https://agentmods.dev/skills/ccbud/ccbuddy/architecture-governance)
Your own site
<a href="https://agentmods.dev/skills/ccbud/ccbuddy/architecture-governance"><img src="https://agentmods.dev/badge/skills/ccbud/ccbuddy/architecture-governance/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 architecture-governance

Your own site · 80×15
<a href="https://agentmods.dev/skills/ccbud/ccbuddy/architecture-governance"><img src="https://agentmods.dev/badge/skills/ccbud/ccbuddy/architecture-governance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,000 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.00045 $0.01000
Opus 5.5 $0.00018 $0.00400
Sonnet 5 $0.00009 $0.00200
Haiku 4.5 $0.00005 $0.00100

Measured yesterday against content hash f21e9ca87a26, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-26, from the pricing page.

Security

Grade A, and why

architecture-governance 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 yesterday.

The scan reads SKILL.md. This mod also ships 4 executable files (references/golden-module/contract.example.ts, references/golden-module/contract.ts, references/golden-module/module.ts, …), 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.

.agents/skills/architecture-governance/SKILL.md · 51 lines

How it starts

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

Architecture governance

Use this skill before editing code in the CCbuddy repository. It is a design guide as well as a gate: the goal is to make the intended architecture obvious before code is generated, so the checker confirms a decision instead of discovering it for the first time.

Before writing code

  1. Identify changed files and their modules with pnpm architecture:check --changed.
  2. Run pnpm architecture:context <module-id> (or the reusable wrapper node .agents/skills/architecture-governance/scripts/context-package.mjs <module-id>). Read the target contract, directly referenced contracts, and any existing relevant spec and tests before opening broad implementation files. Do not assume a documentation or test path exists; verify it in the checkout.
  3. Write or update the spec before implementation; create its directory when needed. State the behavior, ownership, invariants, failure semantics, and migration boundary in the spec.
  4. Make a short design decision before coding:
    • One owner: name the single component that owns each piece of mutable state. Other layers read through its contract and send commands; they do not keep a second accepted queue, cache, or derived truth.
    • One path: reuse an existing command, service, hook, adapter, or contract when it already expresses the behavior. Do not create a parallel helper for the same responsibility.
    • Explicit boundaries: choose the layer for every new file and the public contract for every cross-module edge. Use the module's declared layers and layerOrder; a file may import only its own layer or lower ones through their public surface. domain is pure (no IO, no await on the world), app decides side effects through ports, adapters executes them, ui depends only on this module's contract.ts. Quick test: needs await? not domain. Knows it is sqlite / MessagePort / a timer? adapters.
    • Explicit time: for asynchronous or remote behavior, write the event order, owner/lease, idempotency key, stale-result rule, replay/resume boundary, and desktop versus mobile delivery kind before implementation.
    • Bounded context: prefer the generated reading package over copying whole implementations into the prompt. Read more only when a contract or test proves it is necessary.
  5. If the change crosses modules or changes state ownership, include the decision in the spec and add or update the module contract before implementation.

Read the full file on GitHub · 51 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. yesterday First seen · 51 lines · 45 tokens per session scan A f21e9ca87a26

Subscribe to this mod's changes

architecture-governance is a skill published in the GitHub repository ccbud/CCBuddy (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 45 tokens to every session and 1,000 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-09-25.

Related

Other skills, from other repositories

context-canvas-reflection

Run one bounded trajectory reflection when repeated same-cause failures, contradicted assumptions, real-use failure after local green, material scope drift, a materially unresolved phase boundary, an unapproved authority-sensitive next effect, or user doubt suggests the current path may be wrong. Use Context Canvas…

phenomenoner/Chatgpt-Codex-App-Plus · 99 tokens

context-canvas-checkpoint

Maintain an optional session task map and explicit retrievable references in Context Canvas Codex. Use when navigation or long-context offload would materially help with goals, decisions, progress, dependencies, blockers, next steps, exploration summaries, large textual tool results, or selective historical…

phenomenoner/Chatgpt-Codex-App-Plus · 88 tokens

operate-a2a-superhub

Operate and diagnose the A2A Superhub product across its CLI, HTTP, and declared MCP/A2A surfaces. Use when the user explicitly asks to inspect a Superhub, create or read Superhub tasks or artifacts, work with Superhub memory/inbox/wakeup/handoffs, validate this product skill, diagnose auth/index/queue/capability…

phenomenoner/Chatgpt-Codex-App-Plus · 132 tokens

requesting-code-review

Pre-commit review: security scan, quality gates, auto-fix.

NousResearch/hermes-agent · 20 tokens

gh-issues

Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…

spinabot/brigade · 116 tokens

example

Example fixture skill for scanner regression coverage.

ndycode/codex-multi-auth · 10 tokens