dev-workflow

A collection of development workflows for researching topics, building features with TDD, and writing infrastructure plans. TDD, or test-driven development, means writing a test before implementing the behavior it checks.

In plain words
What is it for?
Use it for cited research, test-led feature implementation, and infrastructure planning documents such as architecture decision records and execution plans.
Why use it?
It gives common development work a repeatable structure, including progress tracking, recorded research, and documented architecture decisions.

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 infraspecdev/tesseract
agentmods
npx agentmods add plugins/infraspecdev/tesseract/dev-workflow
Clone the repo
git clone --depth 1 https://github.com/infraspecdev/tesseract

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-workflow 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.

dev-workflow/.claude-plugin/plugin.json · 11 lines

What it actually says

{
  "name": "dev-workflow",
  "description": "General-purpose development workflow skills: structured research with citations, TDD-based feature implementation with progress tracking, and infrastructure planning document generation (ADR + detailed execution plans)",
  "author": {
    "name": "Ashwini Manoj"
  },
  "repository": "https://github.com/infraspecdev/tesseract",
  "license": "MIT",
  "keywords": ["research", "feature", "tdd", "workflow", "implementation", "planning", "adr", "plan-docs", "architecture", "plan-review", "review", "scoring"]
}
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 · 11 lines scan A c038cb44fb49

Subscribe to this mod's changes

dev-workflow is a plugin published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 2mo 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.