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.
git clone --depth 1 https://github.com/ANcpLua/ancplua-claude-pluginsWrote 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/rules/ancplua/ancplua-claude-plugins/project-config)<a href="https://agentmods.dev/rules/ancplua/ancplua-claude-plugins/project-config"><img src="https://agentmods.dev/badge/rules/ancplua/ancplua-claude-plugins/project-config/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/rules/ancplua/ancplua-claude-plugins/project-config"><img src="https://agentmods.dev/badge/rules/ancplua/ancplua-claude-plugins/project-config.svg" alt="Reviewed on agentmods" width="80" 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.01174 | $0.01174 |
| Opus 5.5 | $0.00470 | $0.00470 |
| Sonnet 5.5 | $0.00235 | $0.00235 |
| Haiku 4.5 | $0.00117 | $0.00117 |
Grade C, and why
project-config scanned grade C with 1 finding 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 21d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Hand-maintained COPY of CLAUDE.md (the canonical guide at the repo root). Keep the body in sync by hand when CLAUDE.md changes. .github/copilot-instructions.md is a SEPARATE hand-maintained doc, not a copy. --> How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ancplua-claude-plugins
A Claude Code plugin marketplace — a git repo that distributes plugins
(commands, agents, skills, hooks, MCP servers) through a marketplace.json
manifest. Claude Code only — no other CLI mirrors, no non-Claude models. The
plugin inventory and install steps live in README.md; this file
is the contributor / dev guide.
Repo structure
.claude-plugin/marketplace.json # Claude Code marketplace manifest (lists every plugin)
plugins/<name>/ # one directory per plugin (17 today)
.github/workflows/ci.yml # JSON + manifest validation — the only gate
automation/ # cron cleanup runner — IGNORE for dev (see automation/policy.md)
README.md # user-facing: what each plugin does + how to install
Plugin layout
Each plugin under plugins/<name>/:
.claude-plugin/plugin.json # required: name, version, description
commands/ agents/ skills/ hooks/ # all optional
README.md # per-plugin docs
Manifest path rule: component/source paths in plugin.json and
marketplace.json must start with ./ (agent paths also end in .md). A bare
path fails recent CLIs with <field>: Invalid input.
Adding or changing a plugin
- Create/edit
plugins/<name>/with a valid.claude-plugin/plugin.json. - Register it in
.claude-plugin/marketplace.json. Each entry needsname,source(./plugins/<name>),description. - Bump the plugin's
versionon any behavioral change (see next section). - Validate, commit, open a PR.
Version bumps reach the cache; edits don't
Installed plugins run from ~/.claude/plugins/cache/<marketplace>/<plugin>/<version>/,
pinned to the installed commit — not from this working tree. /plugin update
re-syncs the cache only when the version string changes; on an equal version it
reports "already at the latest" and keeps running the old code. A fix committed
without a version bump never reaches the running plugin.
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.
- 21d ago Changed · +15 tokens per session c00b76768f10
- 2mo ago First seen · 107 lines · 1,159 tokens per session scan C 446733e31e6e
project-config is a cursor rule published in the GitHub repository ANcpLua/ancplua-claude-plugins (6 stars, last pushed 13d ago), licensed MIT. It adds 1,174 tokens to every session, about $0.0047 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.