Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add SteveGJones/ai-first-sdlc-practices/plugin install sdlc-workflowsWrote 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/skills/stevegjones/ai-first-sdlc-practices/workflows-run)<a href="https://agentmods.dev/skills/stevegjones/ai-first-sdlc-practices/workflows-run"><img src="https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/workflows-run/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/skills/stevegjones/ai-first-sdlc-practices/workflows-run"><img src="https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/workflows-run.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.00025 | $0.04343 |
| Opus 5.5 | $0.00010 | $0.01737 |
| Sonnet 5.5 | $0.00005 | $0.00869 |
| Haiku 4.5 | $0.00003 | $0.00434 |
Grade A, and why
workflows-run 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 1mo 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 — 419 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run SDLC Workflow
Execute a named SDLC workflow via the Archon CLI.
Arguments
- First argument: workflow name (e.g.,
sdlc-parallel-review) - Remaining arguments: passed through to Archon as workflow arguments
Steps
1. Verify Archon is installed and on PATH
The upstream installer places archon at ~/.bun/bin/archon, which is
not on the default macOS PATH. Distinguish between truly missing and
"installed but not discoverable":
if command -v archon >/dev/null 2>&1; then
: # on PATH — proceed
elif [ -x "$HOME/.bun/bin/archon" ]; then
echo "Archon is installed at ~/.bun/bin/archon but that directory"
echo "is not on your PATH. For this session, run:"
echo ""
echo " export PATH=\"\$HOME/.bun/bin:\$PATH\""
echo ""
echo "For a permanent fix (recommended):"
echo " echo 'export PATH=\"\$HOME/.bun/bin:\$PATH\"' >> ~/.zshrc"
echo " # then open a new terminal"
echo ""
echo "Or re-run /sdlc-workflows:workflows-setup --health-check to"
echo "diagnose."
exit 1
else
echo "Archon is not installed. Run /sdlc-workflows:workflows-setup first."
exit 1
fi
Do NOT silently fall back to $HOME/.bun/bin/archon — that hides the
real problem (PATH misconfiguration) and the user will hit it again
the next time they open a shell. Fix the environment, not the
symptom.
2. Verify workflow exists
Run archon workflow list 2>/dev/null and check if the requested workflow name appears.
If not found:
Workflow '{name}' not found. Available workflows:
{list from archon workflow list}
To install SDLC workflows, run /sdlc-workflows:workflows-setup
2b. Preprocess for containerised execution (if workflow has team images)
Check if any node in the workflow has an image: field:
python3 -c "
import yaml
from pathlib import Path
wf = yaml.safe_load(Path('.archon/workflows/<workflow-name>.yaml').read_text())
has_images = any('image' in n for n in wf.get('nodes', []))
print('NEEDS_PREPROCESSING' if has_images else 'NATIVE')
"
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.
- 1mo ago First seen · 419 lines · 25 tokens per session scan E 586950d0d680
workflows-run is a skill published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 15d ago), licensed MIT. It adds 25 tokens to every session and 4,343 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
remove
Remove a deployed framework or addon from the current workspace.