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.
npx skills add hashiiiii/rules-for-ai --skill hashiiiii-issuesgit clone --depth 1 https://github.com/hashiiiii/rules-for-aiWrote 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/skills/hashiiiii/rules-for-ai/hashiiiii-issues)<a href="https://agentmods.dev/skills/hashiiiii/rules-for-ai/hashiiiii-issues"><img src="https://agentmods.dev/badge/skills/hashiiiii/rules-for-ai/hashiiiii-issues/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/skills/hashiiiii/rules-for-ai/hashiiiii-issues"><img src="https://agentmods.dev/badge/skills/hashiiiii/rules-for-ai/hashiiiii-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00022 | $0.00614 |
| Opus 5 | $0.00011 | $0.00307 |
| Sonnet 5 | $0.00004 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
hashiiiii-issues 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 9d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Conventions
Use the same headings and order in every issue body.
Locale
Before you draft an issue, resolve its language:
- If project instructions specify an issue language, use that language.
- If project instructions do not specify a language, use the resolved
issueskey from the context. - If the context has no resolved keys, read the first existing locale file.
- Use this file order: local, project, user, and bundled
LOCALE.default.md. - Use
<absolute-git-dir>/rules-for-ai/LOCALE.mdfor the local file. - Use
<repo>/.rules-for-ai/LOCALE.mdfor the project file. - Use
${XDG_CONFIG_HOME:-${HOME:-}/.config}/rules-for-ai/LOCALE.mdfor the user file. - If no locale file exists, use
en_US. - Use the
issueslanguage for the issue title and body.
Always write the section headings in English. Do not change the template structure.
If issues is ja_JP, keep the English headings. Write the text below each heading in Japanese.
When to Use
- Before
gh issue create - Before you edit an issue body
- If the user asks you to draft an issue
Issue Body Template
Use these exact headings in this order:
## Background
## Problem
## Scope
### In scope
### Out of scope
## Design
## Acceptance criteria
## Notes
Section Guide
| Section | Purpose |
|---|---|
| Background | Explain the context, reason, and earlier decisions. |
| Problem | Describe current defects or missing behavior. |
| Scope / In scope | List the required deliverables. |
| Scope / Out of scope | List the excluded items. |
| Design | Describe the method, alternatives, and important decisions. |
| Acceptance criteria | Give an objective checklist for approval or closure. |
| Notes | Add links, dependencies, open questions, and later work. |
Use - [ ] checkboxes in Acceptance criteria. Each item must have an objective result.
Creating an Issue
gh issue create --title "<title>" --body "$(cat <<'EOF'
## Background
## Problem
## Scope
### In scope
### Out of scope
## Design
## Acceptance criteria
- [ ]
## Notes
EOF
)"
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.
- 9d ago First seen · 104 lines · 22 tokens per session scan A 01b0e985fd35
hashiiiii-issues is a skill published in the GitHub repository hashiiiii/rules-for-ai (10 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 614 once invoked, about $0.0001 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 skills, from other repositories
to-issues
Break a plan or PRD into vertical-slice issues on the project issue tracker.
to-prd
Synthesize the current conversation into a PRD and publish to the issue tracker. No interview — use what you already know.
triage
Move issues and external PRs through triage roles — categorise, verify, grill if needed, write agent-ready briefs.
yida-agent-center
An agent-management tool for Yida, a business workflow platform. It manages temporary substitutes who handle or submit approval processes for current employees or departed employees.
yida-voc
A template for organising user feedback (VOC, or voice of the customer) about problems, requests, and performance issues in the Yida platform.
plan-to-issues
Convert any phased plan file, or a conversation about what to build, into labelled GitHub issues under one tracking epic mapping each issue to its source task. No plan file required. Don't use for writing plans, resolving issues, or triage.