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 paultyng/skill-issue --skill analyze-knowledgegit clone --depth 1 https://github.com/paultyng/skill-issueWrote 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/paultyng/skill-issue/analyze-knowledge)<a href="https://agentmods.dev/skills/paultyng/skill-issue/analyze-knowledge"><img src="https://agentmods.dev/badge/skills/paultyng/skill-issue/analyze-knowledge/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/paultyng/skill-issue/analyze-knowledge"><img src="https://agentmods.dev/badge/skills/paultyng/skill-issue/analyze-knowledge.svg" alt="Reviewed on agentmods" width="80" 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.00057 | $0.01856 |
| Opus 5.5 | $0.00023 | $0.00742 |
| Sonnet 5.5 | $0.00011 | $0.00371 |
| Haiku 4.5 | $0.00006 | $0.00186 |
Grade A, and why
analyze-knowledge 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 1mo 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Knowledge
Analyze git history to surface code expertise, suggest reviewers, and assess knowledge concentration risk.
1. Determine Mode and Scope
Auto-detect from user intent:
| Mode | Triggers | Default scope |
|---|---|---|
| Reviewer | "who should review", "find reviewers", "suggest reviewers" | Changed files: git diff --name-only $(git merge-base HEAD main)..HEAD |
| Distribution | "who knows", "lottery factor", "bus factor", "knowledge spread", "expertise" | User-specified directory, or repo root |
If scope is ambiguous, ask. Accept:
- Explicit paths or globs
- A PR number (extract changed files via
gh pr diff --name-only) - A directory
- "whole repo" (default for distribution mode)
Exclude generated files: check for // Code generated or DO NOT EDIT headers.
2. Normalize Authors
# Check for .mailmap
if [ -f .mailmap ]; then
MAILMAP_FLAG="--use-mailmap"
else
MAILMAP_FLAG=""
fi
- Pass
$MAILMAP_FLAGto all git commands. - If no
.mailmap, group by author name (not email) to merge multiple addresses. - Filter bots: exclude authors matching
[bot],dependabot,renovate,github-actions, or emails containing[email protected]with non-human names.
2.5. Fan out for broad scope
When scope is large, delegate per-area data collection to subagents so main context never sees raw blame/log output for hundreds of files. Aligns with parallelize-subagents (delegate when output would flood main context) and delegate-investigation (read-only history work belongs in Explore).
| Trigger | Strategy |
|---|---|
| Distribution mode, "whole repo" or >20 directories in scope | One Explore subagent per top-level directory; each runs its tiered collection and returns the per-area summary only. |
| Reviewer mode, >20 changed files | Batch files in groups of ~10; one Explore subagent per batch returning per-file expert lists. |
| Tier 3 line-level on >5 files | One Explore subagent per file (blame output is voluminous). |
| Anything smaller | Run inline. Don't spin up a subagent for one git shortlog. |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 181 lines · 57 tokens per session scan A 75184962999d
analyze-knowledge is a skill published in the GitHub repository paultyng/skill-issue (8 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 1,856 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
gh-contribution-planner
Daily GitHub contribution planner — analyzes the gh-logged-in user's non-archived repos (owned + forks) and recent contributions, produces a prioritized plan, halts for approval, then dispatches parallel sub-agents to execute approved items via existing PR/CI/review skills.
fix-merge-conflicts
Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution.
swarm-handoff
Create artifact/commit file handoffs for Agent Toolkit swarms with worktree-per-writer, branch, and promotion integration.
worktree
Manage Git worktrees per writer for Agent Toolkit swarms — isolated branches, handoff promotion, and cleanup.
gh-address-comments
Triage and address open GitHub PR review and conversation comments using the gh CLI. Use when the user wants to "address PR comments", "resolve review threads", or "respond to reviewers" on the current branch's pull request.
project
Clone, index, and orchestrate multi-repo work via agent-toolkit project — symlinks, quick access, and swarm workspaces.