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 agentmods add instructions/qte77/gha-issue-triage/agents-mdgit clone --depth 1 https://github.com/qte77/gha-issue-triageWrote 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/instructions/qte77/gha-issue-triage/agents-md)<a href="https://agentmods.dev/instructions/qte77/gha-issue-triage/agents-md"><img src="https://agentmods.dev/badge/instructions/qte77/gha-issue-triage/agents-md.svg" alt="Measured on agentmods" 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.01305 | $0.01305 |
| Opus 5 | $0.00652 | $0.00652 |
| Sonnet 5 | $0.00261 | $0.00261 |
| Haiku 4.5 | $0.00130 | $0.00130 |
Grade A, and why
gha-issue-triage AGENTS.md 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 5d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions for gha-issue-triage
Behavioral rules and compliance requirements for AI coding agents contributing
to this repository. For project overview see README.md; for
integration paths and troubleshooting see
docs/integrations.md; for boundary failure policies
see docs/architecture.md.
Core principles (MANDATORY)
These principles override all other guidance when conflicts arise.
- KISS — simplest solution that works. Clear over clever.
- DRY — single source of truth. Reference, don't duplicate.
- YAGNI — implement only what's requested. No speculative features.
- Concise and focused — minimal code/text for task. Touch only task-related code.
- Reuse and extend — use existing patterns and dependencies. Don't rebuild.
- Root-cause and first-principles — understand the why. Solve root problems.
- Resolve ambiguity — clarify vague requirements before acting. Never assume missing context.
Behavioral rules
- Never assume missing context — ask if uncertain about requirements.
- Never hallucinate libraries — only use packages verified in
pyproject.toml. - Never delete existing code unless explicitly instructed or refactoring is documented in the PR description.
- Always confirm file paths exist before referencing in code or tests.
- Document new patterns in the PR description (not via separate sidecar files unless explicitly asked).
Repository conventions
These are non-negotiable for any PR landing on main:
- SHA-pin every
uses:in workflows andaction.yaml— full-length commit SHA, never a tag/branch. Enforced by reposha_pinning_required: truepolicy. - Squash-only merge — repo ruleset
15253739allowssquashexclusively. - Required signatures — commits on
mainmust be cryptographically signed (GPG/SSH/web-flow). CLI commits without local signing config require--adminongh pr merge(GitHub web-flow signs the squash commit). - Linear history — no merge commits on
main. - Required status checks —
CodeFactor+CodeQLmust pass before merge. - No
${{ github.event.* }}interpolation inrun:— caller inputs flow throughenv:and dereference as$VARin shell. See the inline note inaction.yaml. - Use bare imports in
src/(from errors import ..., notfrom src.errors import ...). The action runs withPYTHONPATH=srconly — there is nosrcpackage on the path at runtime. Tests can use either form (pytest pythonpath includes.).
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.
- 5d ago First seen · 106 lines · 1,305 tokens per session scan A 6794bc8fc995
gha-issue-triage AGENTS.md is an instructions file published in the GitHub repository qte77/gha-issue-triage (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,305 tokens to every session, about $0.0065 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 instructions, from other repositories
gh-aw AGENTS.md
AGENTS.md instructions for github/gh-aw, covering github agentic workflows (gh-aw), important note: gh-aw vs github copilot cli, ambient context (first invocation), critical rules (always applicable) and upstream-managed workflow sources (read-only in this repo).
run-gemini-cli GEMINI.md
Instructions for google-github-actions/run-gemini-cli, covering guidelines for developing this github action, core principles for this action and your role in development.
dev_agent
Expert engineer for this GitHub Action.
ASE CLAUDE.md
Claude Code instructions for PurCL/ASE, covering claude.md, repository purpose, repository structure, data schema and label taxonomy.
opencoverage copilot-instructions.md
Instructions for arxdsilva/opencoverage, covering copilot instructions for coverage-api, mission, core architecture: hexagonal (ports and adapters), required layers and go language standards.
scaffold AGENTS.md
AGENTS.md instructions for AlexSkrypnyk/scaffold, covering agents.md, project overview, php application architecture, symfony console application and adding new commands.