GitHub Agentic Workflows is a GitHub CLI extension that lets developers define AI-assisted repository automation in Markdown and run it through GitHub Actions. It is intended for tasks requiring interpretation or reasoning, such as issue triage, pull-request review, CI investigation, documentation maintenance, and dependency analysis. The catalogue entries provide skills and agents for working with these workflows.
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 github/gh-aw --skill history-hygienegit clone --depth 1 https://github.com/github/gh-awWrote 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/github/gh-aw/history-hygiene)<a href="https://agentmods.dev/skills/github/gh-aw/history-hygiene"><img src="https://agentmods.dev/badge/skills/github/gh-aw/history-hygiene/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/github/gh-aw/history-hygiene"><img src="https://agentmods.dev/badge/skills/github/gh-aw/history-hygiene.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.00018 | $0.00366 |
| Opus 5.5 | $0.00007 | $0.00146 |
| Sonnet 5.5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
history-hygiene 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- history-hygiene — 100% identical, 24 lines differ
- history-hygiene — 100% identical, 0 lines differ
- history-hygiene — 100% identical, 0 lines differ
- history-hygiene — 100% identical, 0 lines differ
- history-hygiene — 100% identical, 0 lines differ
- history-hygiene — 100% identical, 0 lines differ
- history-hygiene — 100% identical, 72 lines differ
- history-hygiene — 100% identical, 0 lines differ
What it actually says
Context
History files (.md files tracking decisions, spawns, outcomes) are read cold by future agents. Stale or incorrect entries poison decision-making downstream. The Kobayashi incident proved this: history said "Brady decided v0.6.0" when Brady had reversed that to v0.8.17. Future spawns read the wrong truth and repeated the mistake.
Patterns
- Record the final outcome, not the initial request.
- Wait for confirmation before writing to history — don't log intermediate states.
- If a decision reverses, update the entry immediately — don't leave stale data.
- One read = one truth. A future agent should never need to cross-reference other files to understand what actually happened.
Examples
✓ Correct:
- "Migration target: v0.8.17 (initially discussed as v0.6.0, corrected by Brady)"
- "Reverted to Node 18 per Brady's explicit request on 2024-01-15"
✗ Incorrect:
- "Brady directed v0.6.0" (when later reversed)
- Recording what was requested instead of what actually happened
- Logging entries before outcome is confirmed
Anti-Patterns
- Writing intermediate or "for now" states to disk
- Attributing decisions without confirming final direction
- Treating history like a draft — history is the source of truth
- Assuming readers will cross-reference or verify; they won't
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 · 37 lines · 18 tokens per session scan A 1087baea8153
history-hygiene is a skill published in the GitHub repository github/gh-aw (5,579 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 366 once invoked, about $0.0001 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.
history-hygiene compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| history-hygienegithub/gh-aw | Skill | 5.6k | yesterday | MIT | A | 18 | Claude Code, Codex |
| watch-prjustincampbell/gh-watch | Skill | 4 | 7d ago | MIT | A | 48 | Claude Code |
| watch-tagjustincampbell/gh-watch | Skill | 4 | 7d ago | MIT | A | 62 | Claude Code |
| watch-branchjustincampbell/gh-watch | Skill | 4 | 7d ago | MIT | A | 45 | Claude Code |
| watch-commitjustincampbell/gh-watch | Skill | 4 | 7d ago | MIT | A | 48 | Claude Code |
| c-githubdaxaur/openpaw | Skill | 177 | 5mo ago | MIT | A | 48 | Claude Code, Codex |
| update-architecture-docsAlexSkrypnyk/scaffold | Skill | 11 | yesterday | GPL-3.0 | A | 46 | Claude Code |