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/romiluz13/cc10x/agent-commonnpx skills add romiluz13/cc10x --skill agent-commongit clone --depth 1 https://github.com/romiluz13/cc10xWhat 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 | $0.00023 | $0.01211 |
| Opus 5 | $0.00012 | $0.00606 |
| Sonnet 5 | $0.00005 | $0.00242 |
| Haiku 4.5 | $0.00002 | $0.00121 |
Grade A, and why
agent-common 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 3d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Common (Shared Preamble)
Memory First (CRITICAL — DO NOT SKIP)
Read memory before any work:
Bash(command="mkdir -p .cc10x")
Read(file_path=".cc10x/activeContext.md")
Read(file_path=".cc10x/patterns.md")
Read(file_path=".cc10x/progress.md")
Memory contains prior decisions, known gotchas, and current context. Without it, you work blind.
Narrower agent protocols win: if your agent doc deliberately narrows this protocol (anti-anchoring reviewers such as code-reviewer skip activeContext.md; plan-gap-reviewer reads no memory at all), follow the agent doc — the narrowing is intentional, not an omission.
Memory ownership: Do NOT edit .cc10x/*.md files directly. Output a ### Memory Notes section. The router persists memory at workflow-final via task-enforced workflow. Sole carve-out: bug-investigator MAY append [DEBUG-N] investigation lines to .cc10x/activeContext.md under ## Debug History ONLY — no other agent, file, or section.
Key anchors:
- activeContext.md:
## Learnings,## Recent Changes - patterns.md:
## Common Gotchas - progress.md:
## Verification
Domain Glossary (read-only)
Read CONTEXT.md at the repo root if present. Use the project's domain vocabulary in all output — test names, variable names, findings, contracts. Respect any ADRs in docs/adr/ for the area you're touching.
Do NOT write or edit CONTEXT.md from this skill. agent-common is loaded by read-only agents (failure-hunter, integration-verifier, code-reviewer) that must never mutate repository artifacts. CONTEXT.md is written inline only by designated shaping phases (planner, exploration DESIGN mode, doc-syncer) via the cc10x:domain-modeling skill. If you discover a glossary contradiction, emit a **Domain proposal:** line in Memory Notes — do not resolve it.
SKILL_HINTS
If your prompt includes SKILL_HINTS, invoke each skill via Skill(skill="{name}") after memory load. Also: after reading patterns.md, if ## Project SKILL_HINTS section exists, invoke each listed skill. If a skill fails to load, note it in Memory Notes and continue.
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.
- 3d ago First seen · 85 lines · 23 tokens per session scan A 28f70a8b60e7
agent-common is a skill published in the GitHub repository romiluz13/cc10x (164 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 1,211 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
create-request
Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /req-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking request status dashboard.…
codex-setup
Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs the commit-msg hook, copies runner scripts. The pre-push gate is opt-in via --with-push-gate. Use when setting up a new project or after updating skills.
codex-code-review
Code review using Codex MCP. Use when: PR review, code audit, second opinion on changes. Not for: doc review (use doc-review), security audit (use security-review). Output: severity-grouped findings + merge gate.
meta-harness-terminal-bench-2
Run one iteration of AgentHarness evolution for Terminal-Bench 2.
meta-harness
Run one iteration of memory system evolution. Called by metaharness.py or interactively via /meta-harness.
adr
Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as docs/features/ /adr- - .md with a 3-digit zero-padded number. Handles the Superseded case: bidirectional linking when a new ADR replaces an old one. Use when: recording why an architectural…