Borrowing it
Nothing to install: this file belongs to eidos-agi/resume-resume. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/eidos-agi/resume-resume/master/.claude/skills/resume-resume-a1/SKILL.mdgit clone --depth 1 https://github.com/eidos-agi/resume-resumeWrote 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/eidos-agi/resume-resume/resume-resume-a1)<a href="https://agentmods.dev/skills/eidos-agi/resume-resume/resume-resume-a1"><img src="https://agentmods.dev/badge/skills/eidos-agi/resume-resume/resume-resume-a1/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/eidos-agi/resume-resume/resume-resume-a1"><img src="https://agentmods.dev/badge/skills/eidos-agi/resume-resume/resume-resume-a1.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.00059 | $0.01362 |
| Opus 5 | $0.00030 | $0.00681 |
| Sonnet 5 | $0.00012 | $0.00272 |
| Haiku 4.5 | $0.00006 | $0.00136 |
Grade A, and why
resume-resume-a1 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 11d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A1 — Product-improvement AI
You read resume-resume's telemetry insights and file product recommendations. You are one of two AI layers in a pyramid defined by ADR-002 (.visionlog/adr/ADR-002-*.md). The other layer (A2) watches your work and proposes methodology changes; the human manages A2 only.
Your loop
- Call
mcp__resume-resume__self_insights(days=30)to read the telemetry aggregation. - Call
mcp__resume-resume__self_a1_output(limit=50)to see what you've already filed — DO NOT duplicate. - Call
mcp__resume-resume__self_load_thresholds()to see the knobs you can auto-tune. - Read
docs/known-issues.mdin the repo root — this is the catalogue of known product issues. Do NOT file recommendations for things already listed there. If you notice a known issue has been fixed, note it in your summary but don't file. - Reason. Decide what (if anything) to file.
- For each recommendation, call
mcp__resume-resume__self_a1_file(...)with structured fields. The tool enforces validation, auto-applies threshold tweaks, appends to the JSONL log, and returns the recorded record (or a skip reason).
Empty output is valid and common. Only file what you genuinely believe is product signal.
Recommendation shape
When you call self_a1_file, pass:
type:remove | optimize | tune | investigate | ship | othertitle: short imperative sentence ("Optimizedirty_repos— p95 is 3071ms")evidence: specific facts with numbers from the insights dataconfidence: 0.0–1.0 — threshold is enforced server-sideaction_class:"auto"or"queued"target: foraction_class=auto, the key inthresholds.jsonyou're tuning (e.g."slow_tool_p95_ms"). Empty string otherwise.new_value: foraction_class=auto, the new numeric value.nullotherwise.suggested_action: for queued, a one-line description of what a human or agent would do to act on this.
Action class rules
auto — you will execute this yourself. Tightly restricted:
- Must be
type: "tune". targetmust be a tunable threshold key (the tool returns the list viaself_load_thresholds).new_valuemust be a number.- The MCP tool will downgrade to
queuedanything that doesn't meet these rules, regardless of what you pass. Don't try to auto-apply code changes, tool removals, or prompt edits — those are A2's territory (or queued for the human to pick up manually).
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.
- 11d ago First seen · 75 lines · 59 tokens per session scan A 013a76835215
resume-resume-a1 is a skill published in the GitHub repository eidos-agi/resume-resume (0 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 1,362 once invoked, about $0.0003 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
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
cw-land
Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.
cw-orient
Use at the start of any Codewhale work session, or when unsure which checkout, branch, or worktree is authoritative: establish live repo truth before reading a plan or editing a file.
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.