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/artemnovichkov/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/artemnovichkov/skills/sdlc)<a href="https://agentmods.dev/plugins/artemnovichkov/skills/sdlc"><img src="https://agentmods.dev/badge/plugins/artemnovichkov/skills/sdlc/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/artemnovichkov/skills/sdlc"><img src="https://agentmods.dev/badge/plugins/artemnovichkov/skills/sdlc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sdlc 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.
What it actually says
{
"name": "sdlc",
"description": "Run an artifact-driven software lifecycle: intent -> spec -> plan -> code -> verify -> review -> monitor, with every stage committed to git",
"version": "1.0.0",
"author": {
"name": "Artem Novichkov",
"email": "[email protected]",
"url": "https://artemnovichkov.com"
},
"keywords": [
"sdlc",
"planning",
"spec",
"workflow",
"code-review",
"evals",
"governance"
],
"license": "MIT",
"commands": [
"./commands/"
],
"hooks": "./hooks/hooks.json"
}
What it installs
The manifest is a name and a version. 1 skill, 8 commands, 1 agent, 1 hook travel with it, and installing the plugin installs all of them — 328 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.
- yesterday First seen · 25 lines scan A b4078d68bd86
sdlc is a plugin published in the GitHub repository artemnovichkov/skills (36 stars, last pushed yesterday), 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-09-07.
Other plugins, from other repositories
instruction-placement
Routes agent-instruction content to the surface that loads it at the right moment. The audit skill sweeps a repository's instruction layer and its ordinary markdown for content whose scope is narrower than the surface carrying it — conventions keyed to one file type or one subtree sitting in an always-loaded CLAUDE.md.
planning
Pre-implementation planning pipeline: chart a too-big, foggy effort as a decision map, diverge on candidate approaches, lock product intent and the engineering contract, route resolved domain language to the domain-driven-design glossary steward, explore the design space, stress-test adversarially, and produce a…
crm
CRM and sales pipeline management for systemprompt.io. Tracks leads from first touch through conversion, manages deals and pipeline stages, drafts and sends emails via Resend API (human-approved, never automatic), produces daily sales strategy briefs, and logs every action as a falsifiable hypothesis. Includes…
capstone
A collection of workflow skills for finishing, documenting, and publishing software projects.
moai-pm
A project-starting hub for Claude Cowork that interviews you about the work, reviews installed add-ons, and creates project-specific instructions, agents, and workflows. It is intended to help both developers and non-developers set up a project.
comfyui-plugin
ComfyUI custom-node pack lifecycle - scaffold a pack, create + seed the repo, open the gitops adoption PR, publish to the Comfy Registry, and add README screenshots.