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.
git clone --depth 1 https://github.com/RonMizrahi/sdlc-graph-engineeringWrote 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/ronmizrahi/sdlc-graph-engineering/sdlc-graph-engineering)<a href="https://agentmods.dev/plugins/ronmizrahi/sdlc-graph-engineering/sdlc-graph-engineering"><img src="https://agentmods.dev/badge/plugins/ronmizrahi/sdlc-graph-engineering/sdlc-graph-engineering/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/ronmizrahi/sdlc-graph-engineering/sdlc-graph-engineering"><img src="https://agentmods.dev/badge/plugins/ronmizrahi/sdlc-graph-engineering/sdlc-graph-engineering.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sdlc-graph-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 2mo 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.
What it actually says
{
"name": "sdlc-graph-engineering",
"displayName": "SDLC Graph Engineering",
"version": "0.6.0",
"description": "Installs graph engineering into a project that has none: turns an existing process — skills, a runbook, a CI config, or a description — into a guarded graph with typed nodes, total exit guards, bounded retry loops, a run-state file, a skipped-step ledger, its own auditor, and an executable eval suite. Domain-agnostic; needs no other plugin installed.",
"author": {
"name": "Ron Mizrahi",
"email": "[email protected]"
},
"homepage": "https://github.com/RonMizrahi/sdlc-graph-engineering",
"repository": "https://github.com/RonMizrahi/sdlc-graph-engineering",
"license": "MIT",
"keywords": [
"graph",
"state-machine",
"workflow",
"sdlc",
"scaffolding",
"resumable"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 202 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.
- 2mo ago First seen · 22 lines scan A 718a957f24d4
sdlc-graph-engineering is a plugin published in the GitHub repository RonMizrahi/sdlc-graph-engineering (10 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.
Other plugins, from other repositories
alfred-dev
Plugin de ingeniería de software: 8 agentes de núcleo, Selina si hay frontend y Lucius bajo demanda. Memoria persistente por proyecto, quality gates y flujos desde la idea hasta la entrega.
engineering-skills
Cross-platform engineering skills across the software lifecycle, with auditable documents, task-sized workflows and self-contained Codex installation.
asdlc
Agentic SDLC workflows: plan a spec or Jira ticket with a human approval gate, build it task by task, review PRs with a three-lens council, and run a pre-delivery quality check.
cortex
Cortex — SDLC Automation Engine. 54 commands, 13 agents, 27 skills, 7 hooks, 18 reference docs. Forge production-ready software from idea to deployment with zero human intervention. Self-contained meta-process skills (brainstorming, planning, TDD, debugging, verification), production-ready frontend bar…
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.