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/VirtusLab-Open-Source/strapi-plugin-mcpWrote 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/virtuslab-open-source/strapi-plugin-mcp/conventional-commits)<a href="https://agentmods.dev/rules/virtuslab-open-source/strapi-plugin-mcp/conventional-commits"><img src="https://agentmods.dev/badge/rules/virtuslab-open-source/strapi-plugin-mcp/conventional-commits/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/virtuslab-open-source/strapi-plugin-mcp/conventional-commits"><img src="https://agentmods.dev/badge/rules/virtuslab-open-source/strapi-plugin-mcp/conventional-commits.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.00010 | $0.00420 |
| Opus 5.5 | $0.00004 | $0.00168 |
| Sonnet 5.5 | $0.00002 | $0.00084 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
conventional-commits 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 1mo 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.
What it actually says
Conventional Commits
Goal
- Keep commit history readable and automatable; enable changelog generation and semantic versioning.
Format
- Header:
type(scope)!: subject- type:
feat,fix,docs,refactor,test,chore,build,ci,perf,style,revert - scope (optional):
admin,server,common,services,content-types,strapi-info,controllers,routes,tooling,repo - ! (optional): breaking change indicator
- subject: imperative, lower case, no trailing period; ≤ 72 chars
- type:
- Body (optional): why the change is made; context and implications
- Footer (optional):
BREAKING CHANGE:description, and issue references likeCloses #123
Rules
- Use present tense, imperative mood in subjects (e.g., "add", "fix", "remove").
- Keep one logical change per commit when possible.
- Prefer scoping to the most specific area touched.
- Mark breaking changes either with
!in the header or aBREAKING CHANGE:footer.
Examples
feat(server): add service-methods tool returning method metadata
fix(content-types): include components in content-type listing
refactor(common)!: unify McpToolDefinitionBuilder args order
docs(admin): document HomePage and translations flow
test(services): add coverage for services.tool
chore(repo): bump dependencies and regenerate lockfile
Anti-patterns
- Bad:
update stuff(no type/scope) - Bad:
fix(missing subject) - Bad:
feat: Added New Feature.(past tense, capitalized, trailing period) - Bad: Giant commits with unrelated changes; split into smaller logical commits.
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.
- 1mo ago First seen · 47 lines · 10 tokens per session scan A d869d14f84c7
conventional-commits is a cursor rule published in the GitHub repository VirtusLab-Open-Source/strapi-plugin-mcp (3 stars, last pushed 8mo ago), licensed MIT. It adds 10 tokens to every session and 420 once invoked, about $0.0000 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-31.
Other cursor rules, from other repositories
windsurfrules
Pare wraps CLI tools in MCP servers returning structured JSON. Always prefer Pare MCP tools over raw CLI.
git-author
Git author identity for commits so GitHub attributes contributions correctly.
pn-no-cursor-commit-trailers
Do not add Cursor IDE trailers or Cursor Agent git authorship.
conventional-commits
Enforce Conventional Commits format for all commit messages.
development-workflow
Cursor rule "development-workflow" from floriscornel/todo-mcp, covering development workflow for todo mcp, testing & quality assurance, commit structure, branch & pr workflow and publication & releases.
71-git-workflow
USE WHEN: working with Git operations, commits, branches.