A project-repair workflow that reads available code and documentation audit reports and applies their prioritized fixes. Documentation means the instructions and reference material maintained alongside the code.

Use it when a project contains code_audit.md, docs_audit.md, or code_audit_exhaustive.md and you want the selected audit recommendations implemented.

It brings related code and documentation problems into one repair process, reducing the chance that a documented change or a code issue is left unresolved.

fix-project — Skill for Claude Code by InstituteforDiseaseModeling

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add InstituteforDiseaseModeling/idm_standards

Claude Code

/plugin install idm-standards

Made for: Claude Code.

Or install idm-standards, the plugin that ships this one along with the rest of its 10 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/institutefordiseasemodeling/idm_standards/fix-project/github.svg)](https://agentmods.dev/skills/institutefordiseasemodeling/idm_standards/fix-project)

Your own site

<a href="https://agentmods.dev/skills/institutefordiseasemodeling/idm_standards/fix-project"><img src="https://agentmods.dev/badge/skills/institutefordiseasemodeling/idm_standards/fix-project/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/institutefordiseasemodeling/idm_standards/fix-project"><img src="https://agentmods.dev/badge/skills/institutefordiseasemodeling/idm_standards/fix-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 111 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,273 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00111	$0.01273
Opus 5.5	$0.00044	$0.00509
Sonnet 5.5	$0.00022	$0.00255
Haiku 4.5	$0.00011	$0.00127

Measured 2mo ago against content hash 8f4f77a07c19, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

fix-project 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 2mo 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.

idm_standards_plugin/skills/fix-project/SKILL.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Apply fixes from whichever IDM audit reports exist in a project — dispatching fix-code for the code report and implementing documentation fixes directly.

Skill version: 2.0_2026.06.10

Step 1: Find the audit reports

In the project directory (argument, or current working directory), look for:

code_audit.md (or, for compatibility with earlier plugin versions, engineering_score.md)
docs_audit.md
code_audit_exhaustive.md

If the invoking context restricts scope (e.g. audit-docs chained here with "act on docs_audit.md only"), honor that. If none of the reports exist, stop and tell the user:

"No audit reports found. Please run /idm-standards:audit-project (or audit-code / audit-docs) first."

If more than one report exists and the scope wasn't restricted, confirm with the user via one AskUserQuestion (multiSelect) which reports to act on — default: all found.

Discover the user config following $CLAUDE_PLUGIN_ROOT/reference/user-config.md (read it now). Apply its directives across both the code and docs fixes below: never implement a suppressed item (config wins over a stale report), but never skip a hard-floor fix (secrets, license, serious correctness).

Choose a version-control strategy once. Before any changes, ask the user with a single AskUserQuestion how to manage version control for this run, offering the same four options fix-code does: one branch + PR for everything, a branch + PR per priority group (smaller, easier-to-review PRs), commit on the current branch with no PR, or edit only, no git. Pass the chosen strategy into fix-code (Step 2) so it doesn't re-ask, and apply the same choice to the docs fixes (Step 3). Confirm branch name(s) before creating them and confirm before pushing or opening any PR. If the project is not a git repository, edit files directly and tell the user.

Step 2: Fix the code

If acting on code_audit.md: invoke the fix-code skill via the Skill tool, passing the project path and the version-control strategy chosen in Step 1 (so fix-code doesn't re-ask). fix-code discovers and applies the config itself, and handles its own planning, confirmation, implementation, and recording of proposed solutions (including the Tier 2/3 lock-artifact question).

Read the full file on GitHub · 69 lines

Changes

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.

2mo ago First seen · 69 lines · 111 tokens per session scan A 8f4f77a07c19

Subscribe to this mod's changes

fix-project is a skill published in the GitHub repository InstituteforDiseaseModeling/idm_standards (2 stars, last pushed 9d ago), licensed MIT. It adds 111 tokens to every session and 1,273 once invoked, about $0.0004 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.

Code review Debugging

sync-bridge

Reviews and guides Chromium Sync Model API (DataTypeSyncBridge) implementations, including DataTypeStore persistence and forwards/backwards compatibility for sync specifics. Use when implementing or reviewing a DataTypeSyncBridge subclass, DataTypeStore usage, sync metadata persistence, conflict resolution, or…

chromium/chromium · 109 tokens

sync-model-processor

Reviews changes to Chromium Sync model internals in components/sync/model/, including ClientTagBasedDataTypeProcessor, ClientTagBasedRemoteUpdateHandler, ProcessorEntity, ProcessorEntityMetadata, and ProcessorEntityTracker. Use when modifying or reviewing processor state transitions, entity metadata tracking, conflict…

chromium/chromium · 98 tokens

adversarial-reviewer

Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…

emdash-cms/emdash · 72 tokens

gsd-ns-review

Invoke this Pi skill with /skill:gsd-ns-review.

open-gsd/gsd-core · 16 tokens

gitnexus

A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.

hashgraph-online/awesome-codex-plugins · 58 tokens

issue

Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…

jeremylongshore/tons-of-skills-marketplace · 115 tokens