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/agent-readiness)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/agent-readiness"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/agent-readiness/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/agent-readiness"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/agent-readiness.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.00085 | $0.01408 |
| Opus 5.5 | $0.00034 | $0.00563 |
| Sonnet 5.5 | $0.00017 | $0.00282 |
| Haiku 4.5 | $0.00009 | $0.00141 |
Grade A, and why
agent-readiness 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 17d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent-Readiness Scanner (MVP)
Role: worker. Scores a single local repository against the Agent-Readiness Scorecard and reports a tier (Agent-Ready / Assisted / Limited / Hostile) with per-criterion evidence.
Not
/harness-audit. This scores the subject repository (your project's build, code quality, docs, and version-control hygiene) from a static checkout./harness-auditaudits the dev-team plugin's own harness (review-agent effectiveness, model tiers, orchestration) from accumulated runtime metrics. Different subject, different input, different output.
Scope (MVP — issue #117)
This MVP uses file-presence/heuristic analyzers only — no CI-platform APIs. It scores the criteria that can be judged from a checkout:
- Build & Env: B2 reproducible env, B3 dependency lock files, B5 composite check command
- Code Quality: C1 formatting, C2 linting, C4 module size (p90 line count)
- Documentation: D1 README, D2 AI instructions, D3 architecture docs, D5 CLAUDE.md size, D6 layered context
- Version Control: V2 pre-commit hooks, V3 commit conventions, V4 dep scanning
D5, D6, B5 (and the manual-review-only D7) implement the AI-friendly repository
rubric in knowledge/ai-friendly-repo-guidelines.md,
the canonical source for the rationale; evidence strings link to its anchors.
Colocated-test and directory-depth criteria are a deferred follow-up.
Score shift (scorecard 1.1-mvp). Adding D5, D6 and B5 changes the
documentation and build_env category percentages, and so the renormalized
overall score, for repos scanned before this version. The shift is accepted;
tier thresholds are unchanged. Compare scores only within one scorecard
version (scanner_version in the JSON).
Criteria that need CI-platform data (coverage, flaky rate, durations, branch
policy — T1–T5, B1, B4, C5, S1–S4, V1) and the org-scale Azure DevOps / Jenkins
discovery from the original plan are deferred to follow-up phases.
Categories with no MVP criterion (test infrastructure, type safety) are reported
as deferred and excluded from the renormalized overall score.
What ships with it
3 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.
- 17d ago Changed · +39 lines 9a9cbfd253d4
- 1mo ago First seen · 67 lines · 85 tokens per session scan A 78df22ce51be
agent-readiness is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 85 tokens to every session and 1,408 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.