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 audit-accomplishmentsgit 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/audit-accomplishments)<a href="https://agentmods.dev/skills/paultyng/skill-issue/audit-accomplishments"><img src="https://agentmods.dev/badge/skills/paultyng/skill-issue/audit-accomplishments/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/audit-accomplishments"><img src="https://agentmods.dev/badge/skills/paultyng/skill-issue/audit-accomplishments.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.00078 | $0.02944 |
| Opus 5 | $0.00039 | $0.01472 |
| Sonnet 5 | $0.00016 | $0.00589 |
| Haiku 4.5 | $0.00008 | $0.00294 |
Grade A, and why
audit-accomplishments 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 9d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Accomplishments
Mine a person's contribution evidence across every source where their work lives, over a configurable window, and emit cited achievement summaries for review prep. Collection only — this skill does not draft the review.
Sibling of audit-history: that skill mines sessions to improve agent config; this one mines work across external systems to surface achievements. The local-history + memory discovery is shared — reuse audit-history Phase 1 rather than re-deriving it.
Inputs
- window — default last 6 months. Accept an override as dates (
2026-01-01..2026-06-24) or duration (3 months). Compute concrete start/end dates up front and state them. - sources — default all (below). Accept a subset override.
- taxonomy (optional) — a review template's dimensions / career-level areas, supplied as an arg or a path. When absent, group by discovered theme only; do not invent a rubric.
- output dir — default
./review-material/in the cwd.
Guardrails
- Read-only across every external system. Never post, edit, comment, transition, or mutate.
- Cite everything. Each claim carries a re-fetchable reference (URL,
file:line, ticket id, transcript UUID) so it can be expanded during drafting. - Completion over creation. Weight what was finished in the window (PR merged, issue resolved), not what was opened or merely discussed.
- No invention or embellishment. If a section has no evidence, say so. Stay grounded in what was found.
Phase 1 — Discover identities & sources (mechanical, read-only)
Resolve who the person is on each source and where to look. Do not summarize yet.
- GitHub —
gh auth statusenumerates logged-in hosts/accounts. Record eachhost+login. The person may have multiple (e.g. work + personal); mine all unless overridden. - Jira — call the Atlassian MCP
atlassianUserInfo(server name varies by install) for the account id;getAccessibleAtlassianResourcesfor the cloud id(s). - Notion — get the self user via the Notion MCP (
get-users/ self lookup). - Slack — resolve the logged-in
user_id(the search tool reports it). Mine two axes, since neither alone is complete: (a) authored —from:<@USERID> after:<start>to enumerate the channels the person posts in (a globalfrom:memisses DMs and needs real keywords, not stopwords), then drive Phase 2 per-channel; (b) mentions of the person —<@USERID> after:<start> -from:<@USERID>andto:<@USERID>, surfacing where others defer to, route work to, or @-mention them. Prefer the<@USERID>token over literal-name search — a common first name is noisy and misses @-mentions entirely. - Local agent histories + memory — reuse
audit-historyPhase 1: Claude Code transcripts under~/.claude/projects/*, Cursor under~/.cursor/projects/*, memory under~/.claude/projects/*/memory/. Filter to files modified in the window.
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.
- 9d ago First seen · 126 lines · 78 tokens per session scan A 870a677881a4
audit-accomplishments is a skill published in the GitHub repository paultyng/skill-issue (9 stars, last pushed 29d ago), licensed MIT. It adds 78 tokens to every session and 2,944 once invoked, about $0.0004 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
collection
Choose which SkillNote skill collection is active for this Codex project. Use when the user says "change collection", "switch skills", "use frontend skills", or "show collections".
confluence-search
Search Confluence using CQL queries, validate syntax, export results, and manage search history. ALWAYS use when user wants to find, search, or query for content.
confluence-comment
Manage comments on Confluence pages - add, get, update, delete, and resolve comments. ALWAYS use for feedback, discussions, and inline annotations.
confluence-property
Manage content properties (custom metadata) on Confluence pages and blog posts. ALWAYS use for custom metadata, key-value data, or application-specific fields.
confluence-space
Manage Confluence spaces - create, list, update, delete, and configure spaces. ALWAYS use when user wants to work with spaces (not individual pages).
confluence-watch
Content watching and notifications. ALWAYS use when user wants to follow content or manage notifications.