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-status)<a href="https://agentmods.dev/skills/stevegjones/ai-first-sdlc-practices/workflows-status"><img src="https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/workflows-status/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-status"><img src="https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/workflows-status.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.01017 |
| Opus 5.5 | $0.00006 | $0.00407 |
| Sonnet 5.5 | $0.00003 | $0.00203 |
| Haiku 4.5 | $0.00002 | $0.00102 |
Grade A, and why
workflows-status 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDLC Workflow Status
Query Archon workflow runs — live + historical — without depending on
archon being on PATH.
Arguments
--running— show currently running workflows only--recent N— show the latest N runs (default 20)<run-id>— show full detail for a specific run, including every node event in order
Steps
1. Query the Archon state
The archon CLI only exposes archon workflow status (active runs, no
run-id filter) and archon workflow list (available workflows, not runs).
Neither covers the ask. Use the query helper instead — it prefers the
REST API on archon serve (if running) and falls back to reading the
SQLite state DB at ~/.archon/archon.db:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/workflows_status_query.py \
[--running | --recent <N> | --run-id <id>]
Additional flags:
--url <base>— override the REST URL (defaulthttp://localhost:3090)--no-rest— skip the REST probe entirely, go straight to SQLite--json— machine-readable output (one JSON object per response)--timeout <sec>— REST probe timeout before falling back (default 1.0)
Behaviour matrix:
archon serve running? |
Output source |
|---|---|
| Yes | REST API — live + historical, richest |
| No | SQLite read — historical + most-recent, read-only |
If neither is available (fresh machine, no Archon state yet), the script
returns (no workflow runs found) cleanly — this is not an error.
Important — Archon UI clickthrough is degraded for CLI-launched runs.
archon serve only renders the rich UI (DAG graph, conversation thread,
live events) for workflows launched through the server. Workflows
started by /sdlc-workflows:workflows-run use the CLI path — they write
to the same SQLite DB and show up in archon workflow status and in
this skill, but the web UI's per-run detail pages will render empty for
them. This is how Archon 1.x scopes the server — not a bug on our side.
For CLI-launched runs use this skill (REST or SQLite), the CLI's own
stderr stream, or docker logs -f.
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 · 97 lines · 16 tokens per session scan A be8d14e677e1
workflows-status is a skill published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 15d ago), licensed MIT. It adds 16 tokens to every session and 1,017 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…