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.
npx agentmods add commands/zekiriabd/sdd-pro/sdd-kill-servergit clone --depth 1 https://github.com/zekiriabd/SDD-ProWrote 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/commands/zekiriabd/sdd-pro/sdd-kill-server)<a href="https://agentmods.dev/commands/zekiriabd/sdd-pro/sdd-kill-server"><img src="https://agentmods.dev/badge/commands/zekiriabd/sdd-pro/sdd-kill-server.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00021 | $0.02890 |
| Opus 5 | $0.00010 | $0.01445 |
| Sonnet 5 | $0.00004 | $0.00578 |
| Haiku 4.5 | $0.00002 | $0.00289 |
Grade A, and why
sdd-kill-server 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 2d 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdd-kill-server — Arrête backend + frontend + console SDD
Utilitaire runtime (depuis v7.0.0) — pendant de
/sdd-serve. Stoppe les 3 process tournant en arrière-plan (Spring Boot / Vite / Fastify console) en les identifiant par port. Idempotent. Aucun agent invoqué, aucune mutation du code.
Arrête les 3 process runtime du projet généré :
- Backend Java / Spring Boot (port lu depuis
application.ymlou défaut stack —8080Spring,5097.NET,8000FastAPI, etc.) - Frontend Node / Vite (port lu depuis
vite.config.tsou défaut5173) - Console SDD (Node / Fastify, port défaut
4000ou envPORT)
Usage :
/sdd-kill-server— kill les 3/sdd-kill-server back— backend seul/sdd-kill-server front— frontend seul/sdd-kill-server console— console seule/sdd-kill-server back front— sous-ensemble/sdd-kill-server --port 5185— kill un port arbitraire (utile pour processes orphelins après crash)
Read-only sur le code généré, mutations limitées au runtime (kill PID).
STEP 1 — Charger Project Config
Read workspace/stack/stack.md ## Project Config + ## Active Tech Specs
pour identifier :
- Backend stack → port défaut canonique :
| Stack | Port défaut | Détection |
|---|---|---|
backend/kotlin-spring-boot |
8080 (ou 44328 si override server.port dans application.yml) |
grep server.port: dans application.yml |
backend/dotnet-minimalapi |
5097 |
grep applicationUrl dans launchSettings.json |
backend/python-fastapi |
8000 |
constante |
backend/node-express |
3000 |
constante |
- Frontend stack → port défaut :
| Stack | Port défaut |
|---|---|
frontend/react (Vite) |
5173 (ou override server.port dans vite.config.ts) |
frontend/vue (Vite) |
5173 |
frontend/angular |
4200 |
frontend/blazor-webassembly |
5097 |
- Console → toujours
4000(HTTPS) défini dansworkspace/console/server.js, override possible via envPORT.
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.
- 2d ago Changed 2137c5f7bfbc
- 4d ago First seen · 284 lines · 21 tokens per session scan A b6155a090a89
sdd-kill-server is a command published in the GitHub repository zekiriabd/SDD-Pro (190 stars, last pushed yesterday), licensed Apache-2.0. It adds 21 tokens to every session and 2,890 once invoked, about $0.0001 per session on Opus 5. 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.