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 brody-0125/my-claude-skillsnpx agentmods add plugins/brody-0125/my-claude-skills/engineering-workflowgit clone --depth 1 https://github.com/brody-0125/my-claude-skillsWrote 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/brody-0125/my-claude-skills/engineering-workflow)<a href="https://agentmods.dev/plugins/brody-0125/my-claude-skills/engineering-workflow"><img src="https://agentmods.dev/badge/plugins/brody-0125/my-claude-skills/engineering-workflow.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
engineering-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 6d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "engineering-workflow",
"description": "Micro-agent system for engineering architecture decisions — DB, BE, IF, SE domains",
"version": "1.0.0",
"hooks": {
"PreToolUse": [
{
"matcher": "Edit|Write",
"hooks": [
{
"type": "command",
"command": "file=$(echo \"$CLAUDE_TOOL_INPUT\" | jq -r '.file_path // .path // empty' 2>/dev/null); if [ -n \"$file\" ] && echo \"$file\" | grep -qiE '(application-prod|secrets|credentials|private-key)'; then echo '{\"decision\":\"block\",\"reason\":\"Production secret file edit blocked\"}'; exit 2; fi"
}
]
}
],
"PostToolUse": [
{
"matcher": "Write",
"hooks": [
{
"type": "command",
"command": "file=$(echo \"$CLAUDE_TOOL_INPUT\" | jq -r '.file_path // .path // empty' 2>/dev/null); if [ -n \"$file\" ] && echo \"$file\" | grep -qE 'constraints\\.json$'; then jq empty \"$file\" 2>/dev/null || { echo '{\"decision\":\"block\",\"reason\":\"constraints.json is not valid JSON\"}'; exit 2; }; fi"
}
]
}
],
"Stop": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "cache_dir=\"$HOME/.claude/cache/engineering-workflow\"; constraints=\"$cache_dir/constraints.json\"; if [ -f \"$constraints\" ]; then session_id=$(jq -r '.session_id // empty' \"$constraints\" 2>/dev/null); if [ -n \"$session_id\" ]; then mkdir -p \"$cache_dir/history\" && cp \"$constraints\" \"$cache_dir/history/${session_id}-constraints.json\"; fi; fi; history_dir=\"$cache_dir/history\"; if [ -d \"$history_dir\" ]; then ls -1t \"$history_dir\"/*-constraints.json 2>/dev/null | tail -n +21 | xargs rm -f 2>/dev/null; fi; progress=\"$cache_dir/progress.json\"; if [ -f \"$progress\" ]; then ts=$(date -u +\"%Y-%m-%dT%H:%M:%SZ\"); jq --arg s completed --arg t \"$ts\" '.status=$s|.completed_at=$t' \"$progress\" > \"$progress.tmp\" 2>/dWhat it installs
The manifest is a name and a version. 1 skill, 6 agents travel with it, and installing the plugin installs all of them — 106 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 6d ago First seen · 41 lines scan A 9508ab888bc2
engineering-workflow is a plugin published in the GitHub repository brody-0125/my-claude-skills (2 stars, last pushed 6mo 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.
Other plugins, from other repositories
task
Chat-first task workflow: grill the plan one question at a time, then capture the discussion at the depth you pick — to-task / to-plan / to-roadmap / to-spec, never a flag — into a Markdown artifact under .task/. No execution skill — any session told to implement the artifact follows its stamped Execution block to a…
workinggenius
A development workflow that walks every piece of work through the six Working Geniuses — Wonder, Invention, Discernment, Galvanizing, Enablement, Tenacity — every stage a command the user types, every checkpoint a live exchange.
simple-statusline-marketplace
A minimal statusline for Claude Code.
simple-statusline
A simple, hackable two-line statusline for Claude Code showing model, git status, context usage, and rate limits.
context-guard
ContextGuard keeps AI coding-agent context lean, safe, and auditable with project-local setup, scans, large-read guards, output trimming/sanitizing, queryable log artifacts, budgeted context packs, tool/MCP schema pruning, statusline visibility, and usage audits.
cprof
Select which Claude account a session uses, by default profile, per-repo pin, or directory rule.