Borrowing it
Nothing to install: this file belongs to rube-de/cc-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rube-de/cc-skills/main/AGENTS.mdgit clone --depth 1 https://github.com/rube-de/cc-skillsWrote 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/instructions/rube-de/cc-skills/agents-md)<a href="https://agentmods.dev/instructions/rube-de/cc-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/rube-de/cc-skills/agents-md.svg" alt="Measured on agentmods" 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.00830 | $0.00830 |
| Opus 5 | $0.00415 | $0.00415 |
| Sonnet 5 | $0.00166 | $0.00166 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
cc-skills AGENTS.md 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 7d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Claude Code skills marketplace — plugins for multi-agent development, AI council reviews, CI code review, project management, plugin development, quality gates, and platform-specific tooling. See .claude-plugin/marketplace.json for the full plugin registry.
Plugin Architecture
Each plugin follows this structure:
plugin-name/
├── agents/ → Agent definitions (subagents, teammates)
├── commands/ → Slash commands (/plugin:command)
├── hooks/ → hooks.json (PreToolUse, PostToolUse, SessionStart)
├── scripts/ → Shell scripts for hooks and validation
└── skills/ → Bundled skills with SKILL.md + references/
See docs/PLUGIN-AUTHORING.md for the full authoring guide.
Dev Environment
- Run
bun installto install dependencies - Check the
namefield inpackage.jsonto confirm the correct package identity — skip the top-level one when looking at plugins - Plugin directories live under
plugins/— each is self-contained - Refer to
.claude-plugin/marketplace.jsonas the single source of truth for all plugin metadata
Git Workflow
- Always run
git fetch origin && git pull origin mainbefore planning or starting any work - Always create a fresh branch off remote main before editing:
git checkout -b <branch-name> origin/main - Never commit directly to
main - Use conventional commits (
feat:,fix:,docs:,chore:, etc.) — semantic-release picks these up
Validation & PRs
- CI plan lives in
.github/workflows/(ci.ymlvalidates on PR,release.ymlruns on push to main) - Run
bun scripts/validate-plugins.mjsand fix any errors before committing — CI runs the same check - After adding or moving plugin directories or updating marketplace entries, re-run validation to catch orphaned plugin directories or missing source paths
- PRs target
main; semantic-release handles versioning on merge — never edit versions by hand - Prompt engineering review: When a change touches agent prompts (
prompt: >blocks, SKILL.md instructions,*-workflow.mdteammate prompts,agents/*.md), review it against known pitfalls indocs/learnings.mdbefore creating the PR. Specifically check: no literal actions in preambles before numbered workflow gates, no dual numbered sequences, imperatives over aphorisms, and no terminology mismatches with existing workflow steps.
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.
- 7d ago First seen · 53 lines · 830 tokens per session scan A 0052540d0159
cc-skills AGENTS.md is an instructions file published in the GitHub repository rube-de/cc-skills (10 stars, last pushed yesterday), licensed MIT. It adds 830 tokens to every session, about $0.0042 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-31.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.