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 skills add flthibau/sample-OpenClaw-on-Azure-with-AI-Foundry --skill speckit-runnergit clone --depth 1 https://github.com/flthibau/sample-OpenClaw-on-Azure-with-AI-FoundryWrote 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/flthibau/sample-openclaw-on-azure-with-ai-foundry/speckit-runner)<a href="https://agentmods.dev/skills/flthibau/sample-openclaw-on-azure-with-ai-foundry/speckit-runner"><img src="https://agentmods.dev/badge/skills/flthibau/sample-openclaw-on-azure-with-ai-foundry/speckit-runner/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/flthibau/sample-openclaw-on-azure-with-ai-foundry/speckit-runner"><img src="https://agentmods.dev/badge/skills/flthibau/sample-openclaw-on-azure-with-ai-foundry/speckit-runner.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.00022 | $0.01019 |
| Opus 5 | $0.00011 | $0.00509 |
| Sonnet 5 | $0.00004 | $0.00204 |
| Haiku 4.5 | $0.00002 | $0.00102 |
Grade A, and why
speckit-runner 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 11d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
speckit-runner (GitHub Spec Kit — Spec-Driven Development)
Structure your development with GitHub Spec Kit: go from requirements to working code through a disciplined, multi-phase process instead of vibe-coding.
What it does
- Initializes a project with Spec Kit templates (
specify init --ai copilot) - Runs phases by delegating to
copilot-coder(Claude Opus 4.6) which has access to the AGENTS.md slash commands - Orchestrates the full pipeline: constitution → specify → clarify → plan → tasks → analyze → implement
Phases
| Phase | Command | Description |
|---|---|---|
| constitution | /speckit.constitution |
Define project principles (quality, security, conventions) |
| specify | /speckit.specify |
Describe what to build (the what, not the how) |
| clarify | /speckit.clarify |
Identify and resolve underspecified areas |
| plan | /speckit.plan |
Create technical implementation plan (stack, architecture) |
| tasks | /speckit.tasks |
Break plan into actionable tasks |
| analyze | /speckit.analyze |
Cross-check consistency before implementation |
| implement | /speckit.implement |
Execute all tasks to build the feature |
| full | All above | Run the complete pipeline end-to-end |
Usage
# 1. Initialize a new spec-driven project
node run.js --init my-api-project
# 2. Run individual phases
node run.js --phase constitution --project ./my-api-project --instruction "Focus on REST API best practices, security, and testing"
node run.js --phase specify --project ./my-api-project --instruction "Build a task management REST API with CRUD operations, user authentication, and team collaboration"
node run.js --phase plan --project ./my-api-project --instruction "Use Node.js with Express, PostgreSQL, JWT auth, and Jest for testing"
node run.js --phase tasks --project ./my-api-project
node run.js --phase analyze --project ./my-api-project
node run.js --phase implement --project ./my-api-project
# Or run the full pipeline in one command
node run.js --phase full --project ./my-api-project --instruction "Build a task management REST API with Node.js, Express, PostgreSQL"
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 89 lines · 22 tokens per session scan A 3cbcd20747d6
speckit-runner is a skill published in the GitHub repository flthibau/sample-OpenClaw-on-Azure-with-AI-Foundry (5 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 1,019 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…