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 romiluz13/cc10x --skill agent-commongit clone --depth 1 https://github.com/romiluz13/cc10xWrote 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/romiluz13/cc10x/agent-common)<a href="https://agentmods.dev/skills/romiluz13/cc10x/agent-common"><img src="https://agentmods.dev/badge/skills/romiluz13/cc10x/agent-common/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/romiluz13/cc10x/agent-common"><img src="https://agentmods.dev/badge/skills/romiluz13/cc10x/agent-common.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 3 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00032 | $0.01897 |
| Opus 5.5 | $0.00013 | $0.00759 |
| Sonnet 5.5 | $0.00006 | $0.00379 |
| Haiku 4.5 | $0.00003 | $0.00190 |
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 10d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Common (Shared Preamble)
Preloaded into every agent except plan-gap-reviewer (it loads no skills and reads no memory, by design). Read-only agents and write agents share it; where your agent doc is narrower or names a role-specific write, your agent doc wins.
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.
Run the mkdir -p .cc10x/ step unless your agent doc is read-only; the router creates .cc10x/ and .cc10x/qa/<workflow>/ for you, so the step is a no-op safety net. Keep the trailing slash: the QA isolation guard's allowlist is the prefix .cc10x/, and it denies the bare form mkdir -p .cc10x in QA plan phases.
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; qa-researcher creates no files and runs no mkdir), follow the agent doc — the narrowing is intentional, not an omission.
Memory ownership: Do NOT edit the memory files (.cc10x/activeContext.md, .cc10x/patterns.md, .cc10x/progress.md) directly. Output your Memory Notes (see Memory Notes Format). The router persists memory at workflow-final via task-enforced workflow. Every other .cc10x/ path you write only where your agent doc names it (the QA agents write under .cc10x/qa/); .cc10x/workflows/* is router-owned. 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)
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.
- 10d ago Changed · +15 lines · +9 tokens per session 670618171d4b
- 1mo 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 10d ago), licensed MIT. It adds 32 tokens to every session and 1,897 once invoked, about $0.0001 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-30.
Other skills, from other repositories
meta-harness
Run one iteration of memory system evolution. Called by metaharness.py or interactively via /meta-harness.
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
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.…
gh-stack
Native stacked pull requests through the github/gh-stack extension. Detects the extension, installs it only after the user approves, resolves the branch chain, and executes gh stack link / gh stack push / gh stack submit --auto under a per-use AskUserQuestion gate. Use when: opening or refreshing a native stack of…
smart-rebase
Smart partial rebase for squash-merge repositories. Auto-detect which commits to keep/drop when base branch was squash-merged into target. Use when: user says 'rebase', 'partial rebase', 'base already merged', 'smart rebase', or /smart-rebase. Not for: simple git rebase (the developer runs it — no skill executes…
remind
A correction helper that checks which project rules or required steps were missed and loads the relevant guidance.