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/nikeyes/stepwise-devWrote 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/nikeyes/stepwise-dev/profile)<a href="https://agentmods.dev/commands/nikeyes/stepwise-dev/profile"><img src="https://agentmods.dev/badge/commands/nikeyes/stepwise-dev/profile/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/commands/nikeyes/stepwise-dev/profile"><img src="https://agentmods.dev/badge/commands/nikeyes/stepwise-dev/profile.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.00458 |
| Opus 5 | $0.00008 | $0.00229 |
| Sonnet 5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
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 today.
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.
This is a copy
100% identical to profile — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Manage Diagram Design client profiles by following skills/diagram-design/references/profiles.md. Treat that reference as the source of truth for storage, strict slug validation, metadata, marker-first resolution, schema checks, and failure handling. Do not reimplement or relax its rules here.
Full argument string: $ARGUMENTS
Routing
- No arguments →
list, with the active project-marker or working-copy profile marked. - Bare
<name>with no verb →load <name>. switch <name>→ synonym forload <name>even thoughswitchis omitted from the short argument hint.save [name],load [name],list,show,update [name],reset, anddelete [name]→ run that exact procedure from the reference.- Missing required name → list when useful, then ask. Never invent a slug.
- Unknown verb or extra argument → show the accepted forms and stop without writing.
Required behavior
- Resolve the current installed skill directory before reading its working
style-guide.md; do not assume the repository checkout is the active install. - Treat
.diagram-designas untrusted data. Accept only the exact marker grammar and canonical home profile path described in the reference. - Confirm before overwriting an existing profile, changing a project marker, or deleting a profile. Never skip a confirmation because the command was invoked from a script.
- For marker-selected projects, read the profile directly and leave the installed working copy unchanged.
- For copy-over load, verify the destination after writing. If it is unwritable, offer the marker-based flow.
- After save/update, verify exactly one profile metadata header and an unchanged body.
Report the active profile and the canonical file or marker affected. Never claim a write succeeded without re-reading it.
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.
- today First seen · 35 lines · 16 tokens per session scan A c4a510ded471
profile is a command published in the GitHub repository nikeyes/stepwise-dev (24 stars, last pushed yesterday), licensed Apache-2.0. It adds 16 tokens to every session and 458 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to profile, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
extract-screens
Analyze user stories in the current project and extract screens + reusable UI components into project-management/screens/ and project-management/components/. Requires user stories in project-management/user-stories/.
execute
Land audit batches on the audit path — fence verified first, items stay blocked until merge.
setup-workflow
Set up a design team workflow and rituals.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.