dev-practices

A development workflow toolkit for quality-focused software projects. It includes test-driven development, task execution, code review, testing guidance, architecture checks, and integration with Beads task management.

In plain words
What is it for?
Use it for TDD, code and architecture reviews, test design and repair, structured task execution, and Beads-based development workflows.
Why use it?
It organizes common engineering checks and development steps around the task lifecycle. This helps teams track requirements, tests, reviews, and completion together.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add postindustria-tech/agentic-toolkit
agentmods
npx agentmods add plugins/postindustria-tech/agentic-toolkit/dev-practices
Clone the repo
git clone --depth 1 https://github.com/postindustria-tech/agentic-toolkit

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

dev-practices 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 yesterday.

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.

plugins/dev-practices/.claude-plugin/plugin.json · 32 lines

What it actually says

{
  "name": "dev-practices",
  "version": "0.4.1",
  "description": "Development practices and workflows for quality-driven software engineering. Provides TDD, session completion, molecular task execution with formula-based atom graphs, multi-agent code review, entity test remediation, obligation-driven test derivation, test source-of-truth auditing, and obligation reclassification. Integrates with beads task management for complete development lifecycle. The molecular executor delegates research, review, and test-design atoms to fresh-context specialized agents (dp-researcher, dp-reviewer, dp-test-author). Includes 6 specialized review agents for architecture, testing, DRY, consistency, layering, and Python practices.",
  "author": {
    "name": "Konst",
    "email": "[email protected]"
  },
  "homepage": "https://github.com/postindustria-tech/agentic-toolkit",
  "repository": "https://github.com/postindustria-tech/agentic-toolkit",
  "keywords": [
    "development-practices",
    "tdd",
    "test-driven-development",
    "testing",
    "git",
    "workflow",
    "session-management",
    "quality-assurance",
    "beads-integration",
    "code-review",
    "architecture",
    "molecular-workflow",
    "formula-execution",
    "obligation-testing",
    "entity-remediation",
    "test-audit",
    "review-agents"
  ],
  "license": "MIT"
}
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. yesterday First seen · 32 lines scan A 14c2c30e4251

Subscribe to this mod's changes

dev-practices is a plugin published in the GitHub repository postindustria-tech/agentic-toolkit (2 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.