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/rterakedis/leanwheel-skills/github-trackingnpx skills add rterakedis/leanwheel-skills --skill github-trackinggit clone --depth 1 https://github.com/rterakedis/leanwheel-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/skills/rterakedis/leanwheel-skills/github-tracking)<a href="https://agentmods.dev/skills/rterakedis/leanwheel-skills/github-tracking"><img src="https://agentmods.dev/badge/skills/rterakedis/leanwheel-skills/github-tracking.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 | $0.00026 | $0.01731 |
| Opus 5 | $0.00013 | $0.00865 |
| Sonnet 5 | $0.00005 | $0.00346 |
| Haiku 4.5 | $0.00003 | $0.00173 |
Grade A, and why
github-tracking 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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 126 lines · 26 tokens per session scan A 8c0592da6021
github-tracking is a skill published in the GitHub repository rterakedis/leanwheel-skills (2 stars, last pushed today), with no licence file. It adds 26 tokens to every session and 1,731 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
architect
Produces Alon's design-doc system BEFORE code: SOURCEOFTRUTH, ARCHITECTUREROADMAP, TODOWORKFLOW, CLAUDE.md (+ modular docs/architecture). Model first: data + invariants → core enforcement → failure paths → API contracts → phased workstream. Use proactively when a new app, feature, or workstream is starting and code…
coordination-audit
Produce a structured organizational diagnostic that quantifies time spent on specification vs coordination vs execution, saved as a persistent audit artifact to $HOME/.ai-first-kit/. Conducts a guided 5-question interview, classifies every workflow structure by actual function, and identifies highest-ROI automation…
synthesizing-pillars
Use when evidence collection is complete for a pillar and need to extract actionable insights. Transforms raw evidence into structured synthesis with patterns and contradictions identified.
step1-write-spec
Gather requirements through structured Q&A, then formalize into a specification document.
ponytail
Forces the laziest solution that actually works — YAGNI, reuse before new code, stdlib before custom, native platform before dependencies, one line before fifty. Levels: lite/full/ultra. Use proactively when a solution is growing beyond the minimum: new abstractions, dependencies, scaffolding "for later", or…
ask-the-council
Convenes a panel of opinionated advisors (parallel Claude subagents, each with a distinct mandate and a forbidden move so they genuinely diverge), then a Chairman synthesis that COMMITS to one recommendation with explicit tradeoffs. Use proactively for any high-stakes design, architecture, or tradeoff decision where…