remediate-arch-evidence

remediate-arch-evidence is a skill for Claude Code from navapbc/digital-service-orchestra. It costs 154 tokens per session (6,715 once invoked), scanned A, original, Apache-2.0.

A remediation tool for project epics flagged by an architecture-versus-evidence audit. It updates the affected epic using patterns that connect architectural decisions to concrete acceptance evidence.

In plain words
What is it for?
Use it to repair named epics marked as needing remediation, including their state descriptions and acceptance criteria.
Why use it?
It helps close gaps where an epic's design claims are not backed by clear, testable details.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents; positional $N argument.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the dso plugin — 37 skills, 4 commands, 53 agents shipped together

Good fit Use it to repair named epics marked as needing remediation, including their state descriptions and acceptance criteria.

Compare 6 skills from other repositories ↓
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 navapbc/digital-service-orchestra
Claude Code
/plugin install dso

Made for: Claude Code.

Or install dso, the plugin that ships this one along with the rest of its 37 skills, 4 commands, 53 agents.

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.

agentmods badge for remediate-arch-evidence

README.md
[![agentmods](https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/remediate-arch-evidence/github.svg)](https://agentmods.dev/skills/navapbc/digital-service-orchestra/remediate-arch-evidence)
Your own site
<a href="https://agentmods.dev/skills/navapbc/digital-service-orchestra/remediate-arch-evidence"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/remediate-arch-evidence/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.

agentmods 80×15 button for remediate-arch-evidence

Your own site · 80×15
<a href="https://agentmods.dev/skills/navapbc/digital-service-orchestra/remediate-arch-evidence"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/remediate-arch-evidence.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 154 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,715 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 2 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00154 $0.06715
Opus 5 $0.00077 $0.03358
Sonnet 5 $0.00031 $0.01343
Haiku 4.5 $0.00015 $0.00671

Measured 9d ago against content hash dba4ea9d4baa, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

remediate-arch-evidence scanned grade A with 2 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.

Reads agent configuration directorieslowAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

AUDIT_PATH_CONFIG=$(grep -E '^remediate_arch_evidence\.audit_path=' "$REPO_ROOT/.claude/dso-config.conf" 2>/dev/null | cut -d= -f2-)

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- `docker`, `docker manifest`, `curl` (container availability, HTTP healthchecks)
plugins/dso/skills/remediate-arch-evidence/SKILL.md · 489 lines

How it starts

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

Remediate Epic — Architecture-vs-Evidence Audit

You are a Principal Software Engineer remediating epics whose original brainstorms did not yet apply the architecture-vs-evidence probes. Apply the established probe-specific patterns (this file's Phase 2 reference templates) and update the epic in place.

Batch mode

The skill defaults to single-epic per invocation but supports batching when:

  • Session is on an opus-tier model with sufficient context (1M context tier);
  • The user has explicitly authorized batching;
  • The orchestrator applies priming-mitigation discipline: re-read each epic's audit findings fresh, resist pattern-matching to prior remediations, tailor each table/SC to that epic's specific state vars and SC structure.

The audit baseline assumes brainstorm-complete deliverables. If the target epic carries brainstorm:complete but its description self-declares as a stub awaiting follow-on brainstorm (e.g., "Run /dso:brainstorm before implementation"), apply the tag-integrity fix in Phase 0 Step 0.4 rather than substantive remediation.

Read the full file on GitHub · 489 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.

  1. 9d ago First seen · 489 lines · 154 tokens per session scan A dba4ea9d4baa

Subscribe to this mod's changes

remediate-arch-evidence is a skill published in the GitHub repository navapbc/digital-service-orchestra (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 154 tokens to every session and 6,715 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

magpie-security-issue-import-from-md

Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.

apache/magpie · 73 tokens