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/blockmatic/basilicWrote 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/blockmatic/basilic/github-actions)<a href="https://agentmods.dev/rules/blockmatic/basilic/github-actions"><img src="https://agentmods.dev/badge/rules/blockmatic/basilic/github-actions/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/blockmatic/basilic/github-actions"><img src="https://agentmods.dev/badge/rules/blockmatic/basilic/github-actions.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.00052 | $0.00052 |
| Opus 5.5 | $0.00021 | $0.00021 |
| Sonnet 5.5 | $0.00010 | $0.00010 |
| Haiku 4.5 | $0.00005 | $0.00005 |
Grade A, and why
github-actions 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 29d 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
Canonical GitHub Actions inspection constraints (gh, not GitHub MCP) live in root AGENTS.md. Do not diverge from that file.
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.
- 29d ago Changed · -3 lines · -101 tokens per session 4f9ed0c9a6e2
- 1mo ago First seen · 10 lines · 153 tokens per session scan A ec6ef26bec39
github-actions is a cursor rule published in the GitHub repository blockmatic/basilic (90 stars, last pushed today), licensed MIT. It adds 52 tokens to every session, about $0.0002 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-09-03.
Other cursor rules, from other repositories
ci-patterns
CI/CD patterns and automation best practices.
ci-integration
CI/CD integration patterns and automation.
hatch3r-security
CQ3 Security Quality measurement rule — supply-chain integrity, auth depth, secret hygiene, OWASP ASI controls; specialist routing to hatch3r-security.
hatch3r-ci-cd
CI/CD pipeline standards covering stage gates, deployment strategies, and rollback procedures.
hatch3r-typescript-patterns
TypeScript and JavaScript typing mechanics — satisfies over as, discriminated unions, branded types, strict utility types, barrel exports, and import ordering.
create-github-action
ROLE: You are an advanced code-generating LLM tasked with creating a reusable, well-tested, production-ready GitHub Action (and its supporting workflows) using Deno 2.