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 skills/github/gh-aw/sergo-examplesnpx skills add github/gh-aw --skill sergo-examplesgit clone --depth 1 https://github.com/github/gh-awWhat 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 | $0.00016 | $0.00479 |
| Opus 5 | $0.00008 | $0.00239 |
| Sonnet 5 | $0.00003 | $0.00096 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
sergo-examples 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 2d 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
Use this skill only when Sergo needs concrete format examples.
Example: cached tools snapshot
{
"last_updated": "2026-01-15T12:00:00Z",
"tools": [
{"name": "tool-name-1", "description": "..."},
{"name": "tool-name-2", "description": "..."}
]
}
Example: strategy history entries
{"date": "2026-01-14", "strategy": "symbol-analysis", "tools": ["find-symbol", "get-definition"], "findings": 3, "tasks_created": 2, "success_score": 8}
{"date": "2026-01-13", "strategy": "type-inspection", "tools": ["get-hover", "get-type"], "findings": 5, "tasks_created": 3, "success_score": 9}
Example: task template
### Task [N]: [Short Title]
**Issue Type**: [Symbol Analysis / Type Inspection / etc.]
**Problem**: [Clear description]
**Location(s)**: [file paths and line references]
**Impact**: Severity, affected files, risk
**Recommendation**: [Specific fix]
**Validation**: Existing tests, Serena verification, related-pattern check, docs if needed
**Estimated Effort**: [Small/Medium/Large]
Example: discussion structure
Follow the reporting skill (headers ###+, <details> for long sections):
### 🔬 Sergo Report: [Strategy Name]
**Date**: [YYYY-MM-DD]
**Strategy**: [Name]
**Success Score**: [X/10]
### Executive Summary
### 🛠️ Serena Tools Update
### 📊 Strategy Selection
### 🔍 Analysis Execution
<details>
<summary><b>📋 Detailed Findings</b></summary>
</details>
### ✅ Improvement Tasks Generated
### 📈 Success Metrics
<details>
<summary><b>📊 Historical Context</b></summary>
</details>
### 🎯 Recommendations
### 🔄 Next Run Preview
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.
- 2d ago First seen · 71 lines · 16 tokens per session scan A 2c7d931397de
sergo-examples is a skill published in the GitHub repository github/gh-aw (5,050 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 479 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-30.
Other skills, from other repositories
c-github
Interact with GitHub using the gh CLI and jq. Manage PRs, issues, repositories, and Actions workflows. Make raw API calls with gh api for anything not covered by built-in commands.
watch-pr
Watch a GitHub pull request for CI status, reviews, comments, merge conflicts, and terminal states using the gh-watch extension. Use when the user wants to monitor a PR, wait for CI, or track PR progress.
watch-tag
Watch a GitHub repository for new tags using the gh-watch extension. Use when the user wants to be notified when a tag is created, when a release is cut, or when a tag that includes a specific commit appears (e.g. "tell me when my merge ships in a release").
watch-branch
Watch a GitHub branch for new commits using the gh-watch extension. Use when the user wants to be notified when new commits are pushed to a branch, monitor main for merges, or track branch activity.
watch-commit
Watch a GitHub commit for CI status changes using the gh-watch extension. Use when the user wants to monitor a commit's CI checks, wait for a build to finish, or track CI progress on a specific SHA.
update-architecture-docs
Generate or update the architecture documentation in docs/content/architecture/. Use on "update architecture docs", "generate architecture documentation", "regenerate architecture docs", or after any structural change to the codebase.