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 saski/arnesto --skill skill-repairgit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/skill-repair)<a href="https://agentmods.dev/skills/saski/arnesto/skill-repair"><img src="https://agentmods.dev/badge/skills/saski/arnesto/skill-repair.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.1 | $0.00043 | $0.00434 |
| Opus 5 | $0.00022 | $0.00217 |
| Sonnet 5 | $0.00009 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
skill-repair 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.
What it actually says
Skill Repair Assistant
You have been tasked with fixing a broken agent skill. After you have modified
the skill's source files to address the reported error, you MUST update the
manifest.json to reflect that the skill is now repaired.
Skill Context
- Skill ID: The unique identifier for the skill (e.g.,
my-skill). - Source Path: Where the skill's source files are located.
- Installed Path: Where the skill is installed/replicated.
- Manifest Path: The absolute path to the
manifest.jsonfile.
Repair Procedure
- Analyze Error: Understand the error message provided in the prompt.
- Fix Installed Path: Fix the issue at the installed path. Since some
skills have multiple files, you MUST list all files in the skill directory
and analyze them collectively to find the root cause (e.g., malformed
SKILL.md, missing resources, or incorrect sub-scripts). - Update Manifest: Once the fix is applied to ALL relevant files, you MUST
update the
manifest.jsonat the Manifest Path.- Find the entry for the skill ID in the
skillsobject. - Set
"status": "installed". - Clear the
"error"field (set tonullor remove it).
- Find the entry for the skill ID in the
- Verification: The UI will automatically detect this change and refresh.
Manifest Example
{
"skills": {
"my-skill": {
"status": "installed",
"disabled": false,
"error": null
}
}
}
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 · 53 lines · 43 tokens per session scan A 7ed4b7eb5d82
skill-repair is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed today), licensed Unlicense. It adds 43 tokens to every session and 434 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
readonly-review
Run a no-network read-only review practice with two explorer steps and one synthesis step.
repo-contracts-and-boundaries
Use when turning architecture, layering, ownership, dependency direction, schemas, structural metrics, quality thresholds, baselines, allowlists, or generated quality snapshots into repository checks.
repo-harness-assessment
Use when evaluating repository agent-readiness, mapping harness roles, choosing the next smallest improvement, or designing and reconciling agent entrypoints such as AGENTS.md, CLAUDE.md, GEMINI.md, Cursor rules, or GitHub instructions.
work-state-and-delivery
Use when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or repository commit-coupling policy.
runtime-evidence-and-tracing
Use when connecting observed behavior, logs, metrics, request IDs, run IDs, screenshots, traces, external dependency results, or artifacts into a runtime evidence loop.
validation-harness-design
Use when designing repository validation commands, doctor scripts, test matrices, JSON or JUnit outputs, CI gates, smoke checks, or harness command surfaces.