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 swingerman/engineernpx agentmods add plugins/swingerman/engineer/marketplacegit clone --depth 1 https://github.com/swingerman/engineerGrade A, and why
disciplined-agentic-engineering 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 2d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "disciplined-agentic-engineering",
"owner": {
"name": "Miklos",
"email": ""
},
"metadata": {
"description": "Disciplined Agentic Engineering — a methodology kit for Claude Code: the engineer, atdd, and crap-analyzer plugins, grounded in Uncle Bob's acceptance-test approach",
"version": "1.14.0"
},
"plugins": [
{
"name": "atdd",
"source": "./",
"description": "Acceptance Test Driven Development for Claude Code. Enforces the ATDD methodology: write Given/When/Then specs first, generate a project-specific test pipeline, maintain two test streams (acceptance + unit). Inspired by Robert C. Martin's acceptance test approach from empire-2025.",
"version": "0.8.4",
"author": {
"name": "Miklos"
},
"homepage": "https://github.com/swingerman/engineer",
"repository": "https://github.com/swingerman/engineer",
"license": "MIT",
"keywords": ["atdd", "acceptance-testing", "tdd", "given-when-then", "spec-driven-design", "uncle-bob", "bdd"],
"category": "development-workflows",
"tags": ["testing", "methodology", "acceptance-tests", "spec-driven-design", "ai-development"]
},
{
"name": "engineer",
"source": "./engineer",
"description": "Disciplined Agentic Engineering (DAE) — methodology kit for Claude Code. Skills that implement the DAE pipeline: feature intake, AC discovery, spec writing, planning, implementation, verification, hardening.",
"version": "0.26.0",
"author": {
"name": "Miklos"
},
"homepage": "https://github.com/swingerman/engineer",
"repository": "https://github.com/swingerman/engineer",
"license": "MIT",
"keywords": ["dae", "disciplined-agentic-engineering", "methodology", "ai-development", "tdd", "atdd", "engineering"],
"category": "development-workflows",
"tags": ["methodology", "ai-development", "engineering-workflow", "spec-driven-design"]
},
{
"What ships with it
1 file beside marketplace.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.
- 2d ago First seen · 60 lines scan A e967fa218973
disciplined-agentic-engineering is a plugin published in the GitHub repository swingerman/engineer (144 stars, last pushed 6d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other plugins, from other repositories
junior-flow
Helps junior developers create technical story markdown from a story tracker.
ensemble-ai
AI SDK skills for OpenAI, and other AI providers for Claude Code.
brana
AI development system — skills, agents, and hooks for systematic software engineering with Claude Code.
8-habit-ai-dev
Anti-Vibe-Coding plugin — 7-step workflow discipline + 8-Habit cross-verification for AI-assisted development.
claude-publish
Publish markdown to blogging platforms: Medium via the gist import flow, with a content-kit (style guide, banners, post naming) that keeps published content on-brand.
testkit
Universal E2E and manual acceptance testing for any repo: test-init generates project test plans (TESTSE2E.md, TESTSMANUAL.md), test-e2e executes them autonomously, test-manual conducts them with you at the controls. Every run writes a timestamped protocol file.