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.
/plugin marketplace add bdfinst/agentic-dev-team/plugin install dev-teamWrote 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/bdfinst/agentic-dev-team/harness-audit)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/harness-audit"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/harness-audit/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/bdfinst/agentic-dev-team/harness-audit"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/harness-audit.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.00081 | $0.09997 |
| Opus 5.5 | $0.00032 | $0.03999 |
| Sonnet 5.5 | $0.00016 | $0.01999 |
| Haiku 4.5 | $0.00008 | $0.01000 |
Grade A, and why
harness-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 1mo 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 — 752 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness Audit
Role: orchestrator. This command analyzes harness effectiveness — it does not modify agents or configuration.
You have been invoked with the /harness-audit command.
Not
/agent-readiness. This audits the dev-team plugin's own harness (review-agent effectiveness, model tiers, orchestration) from accumulated runtime metrics inmetrics/./agent-readinessscores the subject repository's readiness for AI-assisted development from a static checkout. Different subject, different input, different output. The inward-facing companion here is/session-review, whosesession-digest.jsonlthis command consumes (Step 1).
Portable executable, repo-relative data (#1653). eval_ablation.py now ships under plugins/dev-team/scripts/ — its --find-latest/--jsonl mode is a generic JSONL reader with no repo-shape assumption, unlike the module's --mode knowledge/--mode agent paths, which stay monorepo-only (they read evals/ fixtures never shipped). The call below is therefore ${CLAUDE_PLUGIN_ROOT}-qualified like any other shipped script; only the --jsonl argument stays bare — metrics/eval-ablation.jsonl is genuinely this repo's own runtime metrics stream, consistent with the note above that this command audits the dev-team plugin's own harness.
Orchestrator constraints
- Do not modify agents or configuration. Produce a report only. All remediation requires human action.
- Write the report to a file. Present only the summary table and next-steps in chat — do not repeat the full report.
- Be concise. Use tables and short sentences. No preambles, no filler.
Parse Arguments
Arguments: $ARGUMENTS
--output <path>: Write report to a specific path. Default:.dev-team-reports/harness-audit-<date>.md--pdf: After writing the report, render it to a sibling PDF viahooks/lib/report_pdf.py, resolving against the actual report path written this run (the--outputoverride when given, else the default). Seeknowledge/report-pdf-integration.md. Additive; non-fatal if no engine is available.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 752 lines · 81 tokens per session scan A 3546f166f542
harness-audit is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 81 tokens to every session and 9,997 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.