agentmods.dev

audit

A workspace audit command for OpenCode, a coding-agent tool. It checks project instructions, settings, extensions, integrations, formatting, and runtime checks against a scoring guide.

In plain words
What is it for?
Use it to assess the quality of an OpenCode setup, find configuration and policy problems, and get copy-ready fixes plus a seven-day improvement plan.
Why use it?
It replaces a manual inspection of scattered project and user configuration files with one structured review. It also identifies risks, assigns scores, and points to the exact files involved.

Command

11 2mo ago A scan 6 tokens original MIT
View the source file Awish021/opencode
Install

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.

agentmods
npx agentmods add commands/awish021/opencode/audit
Clone the repo
git clone --depth 1 https://github.com/Awish021/opencode
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 368 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00006 $0.00368
Opus 5 $0.00003 $0.00184
Sonnet 5 $0.00001 $0.00074
Haiku 4.5 $0.00001 $0.00037

Measured yesterday against content hash 67a4c30dd900, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

audit 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 yesterday.

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.

commands/audit.md · 36 lines

What it actually says

Run an OpenCode-native audit for this workspace.

Use OPENCODE-AUDIT.md as the scoring authority.

Scope:

  • AGENTS.md policy quality
  • OpenCode config/model/permission quality
  • agents, commands, and skills quality
  • MCP and plugin integration posture
  • formatter and runtime quality gates

Discovery:

  1. Inspect both project and global locations when available:
    • AGENTS.md, .opencode/AGENTS.md, ~/.config/opencode/AGENTS.md
    • .opencode/config.json, .opencode/opencode.json, .opencode/opencode.jsonc
    • ~/.config/opencode/config.json, ~/.config/opencode/opencode.json, ~/.config/opencode/opencode.jsonc
    • .opencode/agents/*.md, ~/.config/opencode/agents/*.md
    • .opencode/commands/*.md, ~/.config/opencode/commands/*.md
    • .opencode/skills/*/SKILL.md, ~/.config/opencode/skills/*/SKILL.md
    • .claude/skills/*/SKILL.md, ~/.claude/skills/*/SKILL.md when present
  2. Cite exact file paths for every major finding.

Output requirements:

  1. Return total score /100 and grade.
  2. Return category scores exactly matching the rubric.
  3. List top risks first.
  4. Provide at least 5 concrete fixes with copy-paste commands/snippets.
  5. Include a 7-day action plan with quick wins first.

If the user provided focus areas in $ARGUMENTS, prioritize those categories but still score all categories.

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.

  1. yesterday First seen · 36 lines · 6 tokens per session scan A 67a4c30dd900

Subscribe to this mod's changes

audit is a command published in the GitHub repository Awish021/opencode (11 stars, last pushed 2mo ago), licensed MIT. It adds 6 tokens to every session and 368 once invoked, about $0.0000 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-30.

PlanningWriting and docs
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens