Borrowing it
Nothing to install: this file belongs to zekiriabd/SDD-Pro. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zekiriabd/SDD-Pro/main/.claude/commands/sdd-profile.mdgit 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-profile)<a href="https://agentmods.dev/commands/zekiriabd/sdd-pro/sdd-profile"><img src="https://agentmods.dev/badge/commands/zekiriabd/sdd-pro/sdd-profile.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.1 | $0.00021 | $0.01225 |
| Opus 5 | $0.00010 | $0.00613 |
| Sonnet 5 | $0.00004 | $0.00245 |
| Haiku 4.5 | $0.00002 | $0.00122 |
Grade A, and why
sdd-profile 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 7d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdd-profile — Gestion des profiles team config (v6.7.2)
⚠️ Commande interne v7.0.0 — invocation manuelle (gouvernance team config, wrapper
manage_profile.py). Pas d'usage pipeline ; outil ops dédié.
Wrapper autour de python .sdd/python/sdd_scripts/manage_profile.py.
Permet d'exporter/importer/lister les profiles ~/.sdd/profiles/{name}.yml,
qui sont des snapshots de ~/.sdd/config.team.yml (le niveau team du
layered config v6.7.1).
Usage :
/sdd-profile export <name>— sauve la team config actuelle comme profile/sdd-profile export <name> --force— overwrite un profile existant/sdd-profile import <name>— charge un profile (backup auto de l'actuel en.bak)/sdd-profile list— liste tous les profiles + active team config/sdd-profile show <name>— affiche le contenu d'un profile/sdd-profile delete <name>— supprime un profile
Garanties :
- Aucune modification de
workspace/stack/stack.md(per-project) - Aucune modification du moteur SDD_Pro
- N'a un effet que sur futures exécutions (la config layered est lue à chaque commande)
- Backup automatique avant overwrite (
.bak)
STEP 1 — Dispatch
Invoquer directement le script Python :
python .sdd/python/sdd_scripts/manage_profile.py {subcommand} {args}
Tous les arguments sont passés tels quels. Le script retourne :
- exit 0 : succès, output sur stdout
- exit 1 : I/O error (profile not found, team config absent)
- exit 2 : misuse (invalid name, profile exists sans --force)
STEP 2 — Exemple workflow
Définir une policy stricte pour une équipe sécurité :
# 1. Configurer ~/.sdd/config.team.yml manuellement
# Ex. CoverageMin: 90, SecurityFailOn: critical, SpecComplianceMode: full
# 2. Sauver comme profile
/sdd-profile export strict-prod
# 3. Lister
/sdd-profile list
# Output:
# - strict-prod
# - dev-only
# Active team config: ~/.sdd/config.team.yml
# 4. Sur un autre projet, basculer en mode dev
/sdd-profile import dev-only
# ✓ profile 'dev-only' loaded → ~/.sdd/config.team.yml
# ↻ existing team config backed up → ~/.sdd/config.team.yml.bak
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.
- 7d ago First seen · 133 lines · 21 tokens per session scan A caae992f70cb
sdd-profile is a command published in the GitHub repository zekiriabd/SDD-Pro (191 stars, last pushed 4d ago), licensed Apache-2.0. It adds 21 tokens to every session and 1,225 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.