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/encoreshao/encore-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/rules/encoreshao/encore-skills/triage-issue)<a href="https://agentmods.dev/rules/encoreshao/encore-skills/triage-issue"><img src="https://agentmods.dev/badge/rules/encoreshao/encore-skills/triage-issue/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/encoreshao/encore-skills/triage-issue"><img src="https://agentmods.dev/badge/rules/encoreshao/encore-skills/triage-issue.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.00054 | $0.00080 |
| Opus 5.5 | $0.00022 | $0.00032 |
| Sonnet 5.5 | $0.00011 | $0.00016 |
| Haiku 4.5 | $0.00005 | $0.00008 |
Grade A, and why
triage-issue 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 2mo 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
@skills/triage-issue/SKILL.md
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.
- 2mo ago First seen · 8 lines · 54 tokens per session scan A 9cd682dadc60
triage-issue is a cursor rule published in the GitHub repository encoreshao/encore-skills (2 stars, last pushed 5d ago), licensed MIT. It adds 54 tokens to every session and 80 once invoked, 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-08-31.
Other cursor rules, from other repositories
roslyn-mcp-version-bump
Auto-bump Version after successful MCP self-build and reload.
changeset
Guidelines for using Changesets (npm run changeset) to manage versioning and changelogs.
fusebase-flow-implementation
Fusebase Flow implementation phase rules. Use when editing source code per a locked spec.
no-tool-contributors
Never add AI coding tools as contributors or co-authors.
github-repo-triage
Triage and maintain GitHub repos — issues, PRs, cherry-picks, releases, publishing.
git
Cursor rule "git" from duongductrong/cursor-kit, covering git conventions, commit messages, types, subject rules and examples.