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 agentmods add skills/kashzod/devloop/specnpx skills add KashZod/devloop --skill specgit clone --depth 1 https://github.com/KashZod/devloopWhat 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 | $0.00044 | $0.04334 |
| Opus 5 | $0.00022 | $0.02167 |
| Sonnet 5 | $0.00009 | $0.00867 |
| Haiku 4.5 | $0.00004 | $0.00433 |
Grade A, and why
spec 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 yesterday.
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 — 482 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Specification Process
Create a specification for the following: $ARGUMENTS
Specifications clarify WHAT to build before implementation begins. Instead of discovering ambiguity mid-implementation (expensive), surface it upfront through structured exploration and clarification, where resolving it costs a question instead of a rewrite.
Mapping to the Explore -> Plan -> Code Loop
| Workflow Phase | Spec Phase | What Happens |
|---|---|---|
| Explore | Phase 1: Explore | Read files, understand context, check .devloop/domain.md |
| Plan | Phase 2: Specify | User stories, acceptance criteria, edge cases |
| Plan | Phase 3: Clarify | Interactive disambiguation (max 5 questions) |
| Plan | Phase 4: Validate | 8-point spec quality checklist |
| Plan | Phase 5: Handoff | Summary report, suggest /plan |
When to Use This Process
| Scope | Approach |
|---|---|
| Trivial (typo, config, rename) | Don't use this skill -- just do it directly |
| Small (well-understood, single concern) | Quick spec shortcut (skip clarification) |
| Medium (multi-concern, some ambiguity) | Full process |
| Large (cross-cutting, unfamiliar domain) | Full process, thorough clarification |
Quick spec shortcut: For small well-understood changes with no domain ambiguity, collapse to: Explore -> Specify -> Validate -> Handoff. Skip clarification entirely. Use when the feature can be described in one sentence and has no competing interpretations.
Scope negotiation: If the request contains 3+ distinct features, recommend splitting into separate specs before proceeding. Each spec should cover one coherent feature with independent user value.
Product vs feature: If the request describes an entire product or system (multiple independent capabilities, separate components, its own installation story), treat it as a product-level spec:
- One user story per major capability (not per implementation task)
- Acceptance criteria verify capability, not component details
- Implementation chunking goes in Notes or during TDD, not as separate specs
- Spec size will exceed the standard guideline, this is expected
What ships with it
3 files 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.
- yesterday First seen · 482 lines · 44 tokens per session scan A 6af98cd75c20
spec is a skill published in the GitHub repository KashZod/devloop (2 stars, last pushed 9d ago), licensed Apache-2.0. It adds 44 tokens to every session and 4,334 once invoked, about $0.0002 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
align
Interview the person before implementation when requirements, scope, expected behavior, design, or an important assumption needs shared agreement.
diff
Use when someone asks to explain or review a GitHub pull request as an evidence-linked, self-contained offline HTML review.
spring-boot-4-conventions
Spring Framework 7 / Spring Boot 4 idioms and defaults. Use when writing or reviewing controllers, services, configuration, HTTP clients, async/virtual-thread code, or anything touching Spring's programming model.
performance-optimization
Spring Boot 4 / JVM performance work — measure first, then fix. Profiling (async-profiler, JFR, JMH), Micrometer, common Spring antipatterns (N+1, unbounded lists, HikariCP sizing, virtual-thread pinning), caching, GC, and SLO-driven work. Used by /plan for risk callouts and by /review to flag perf regressions.
maven-harness-pom
Reference Maven POM fragments for the full harness — Spotless, Checkstyle, SpotBugs, Error Prone, JaCoCo, PIT, OpenAPI generator + diff, OWASP dependency check, Surefire/Failsafe. Use when wiring the harness into a new project or upgrading a brownfield POM.
shipping-and-launch
Pre-deploy hygiene for a Spring Boot 4 feature — verify gates, capture rollback plan, sign off observability, generate release notes, and stage the rollout. Used by /ship after /review approves the diff. The agent never deploys; it produces the plan a human executes.