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.
/plugin marketplace add dgambhir01/ado-testcraftnpx agentmods add plugins/dgambhir01/ado-testcraft/ado-testcraftgit clone --depth 1 https://github.com/dgambhir01/ado-testcraftWrote 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/plugins/dgambhir01/ado-testcraft/ado-testcraft)<a href="https://agentmods.dev/plugins/dgambhir01/ado-testcraft/ado-testcraft"><img src="https://agentmods.dev/badge/plugins/dgambhir01/ado-testcraft/ado-testcraft.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
ado-testcraft 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 4d 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.
This is a copy
86% identical to ado-testcraft marketplace — 26 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"name": "ado-testcraft",
"description": "Generates structured test cases from Azure DevOps User Stories. Covers positive, negative, edge cases, and boundary values using QE best practices.",
"version": "1.1.0",
"author": {
"name": "Dheeraj Gambhir",
"url": "https://github.com/dgambhir01"
},
"homepage": "https://github.com/dgambhir01/ado-testcraft",
"repository": "https://github.com/dgambhir01/ado-testcraft",
"license": "MIT",
"keywords": ["testing", "qa", "azure-devops", "test-cases", "qe", "test-generation"]
}
What it installs
The manifest is a name and a version. 3 skills, 1 MCP server travel with it, and installing the plugin installs all of them — 133 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json 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.
- 4d ago First seen · 14 lines scan A b5e3d03d9f46
ado-testcraft is a plugin published in the GitHub repository dgambhir01/ado-testcraft (1 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. It is 86% identical to ado-testcraft marketplace, differing in 26 lines, and is treated as a copy.
Other plugins, from other repositories
audit
Manifest-driven, model-aware, test-driven audit/fix pipeline. Ships /audit:status|next|run|phase|review|resume|report (execution), /audit:init (multi-agent manifest generation with an approval gate — decline parks phases as proposals), /audit:propose (list/materialize/drop parked phase proposals), /audit:task (task…
workbench
Ticket-to-PR development workflow: triage, plan with verified citations, implement inside the plan, review, commit, PR. Pluggable issue trackers (Jira, Azure DevOps, GitHub Issues) or a backlog in the repo, so it works with no tracker at all.
han-communication
Foundational communication plugin for the Han suite. Owns the canonical readability standard, the writing-voice profile, and the explanation standard for talking to a reader who will not implement the work, plus the readability-guidance skill that surfaces the first two into a calling skill's own context for in-voice…
handbook-agent-spec-kit
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation.
go-ultimate
Opinionated Go development skill — architecture, conventions, production readiness, repo/CI hygiene, review, and MCP/agent patterns.
claude-code
Meta-tools for Claude Code configuration and customization.