agentmods.dev

WINDSURF

WINDSURF is an agent for Claude Code from loki-ai-ch/spec-manager. It costs 0 tokens per session (558 once invoked), scanned A, a copy of AGENTS, MIT.

A Windsurf project entry file that directs the coding agent to use the spec-manager workflow for feature work. Windsurf is a coding environment that reads project rules from a file named .windsurfrules.

In plain words
What is it for?
Use it to route feature development through spec-manager, enforce approved implementation specifications, and define verification requirements for completed tasks.
Why use it?
It gives Windsurf consistent local rules for requiring reviewed specifications before code changes and for keeping project decisions and task records in the repository.

Agent for Claude Code

not rated 5 1mo ago A scan 0 tokens copy · 81% MIT
View the source file loki-ai-ch/spec-manager
Install

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.

agentmods
npx agentmods add agents/loki-ai-ch/spec-manager/windsurf
Clone the repo
git clone --depth 1 https://github.com/loki-ai-ch/spec-manager

Made for: Claude Code.

Wrote 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.

agentmods badge for WINDSURF

README.md
[![agentmods](https://agentmods.dev/badge/agents/loki-ai-ch/spec-manager/windsurf.svg)](https://agentmods.dev/agents/loki-ai-ch/spec-manager/windsurf)
Your own site
<a href="https://agentmods.dev/agents/loki-ai-ch/spec-manager/windsurf"><img src="https://agentmods.dev/badge/agents/loki-ai-ch/spec-manager/windsurf.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 558 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 81% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00558
Opus 5 $0.00000 $0.00279
Sonnet 5 $0.00000 $0.00112
Haiku 4.5 $0.00000 $0.00056

Measured 3d ago against content hash 893e2308e650, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

WINDSURF 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 3d 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.

Origin

This is a copy

81% identical to AGENTS — 3 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.

.claude/skills/spec-manager/templates/agents/WINDSURF.md · 31 lines

How it starts

The opening of the file, as written. The whole thing — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.

spec-manager Workflow Capsule

This file is the spec-manager entrypoint for Windsurf. Windsurf reads project rules from .windsurfrules; route feature work through spec-manager.

This project uses spec-manager for local-first spec-driven development. Specs, tasks, decisions, changes, and audit data are stored as markdown/JSON files in the repository.

Unified Rules

  • Feature work MUST go through spec-manager.
  • New or non-trivial work follows L1 -> L2 -> L3 -> Agent Task.
  • Never write implementation code without a frozen L3 spec.
  • L1/L2 approval advances draft -> confirmed; one explicit L3 approval (an explicit user approval) advances draft -> frozen.
  • Before code edits, read the frozen L3 spec and create/start an Agent Task.
  • planJson coveredSpecs MUST include the current L3 specCode.
  • If adaptive workflow is enabled, Task creation records a standard or governed Profile snapshot; governed requires the frozen L3 to declare ## 关键验收标准 with valid AC IDs, and task complete requires successful verification evidence covering every critical AC. standard reports missing coverage as warnings. Use spec-manager project profile recommend --request "<work>" for a deterministic, explainable recommendation; it does not auto-enable adaptive workflow and is not a hidden gate. Use spec-manager project profile metrics [--topic <topic>] [--json] for a read-only governance report over Profile adoption, governed coverage gaps, standard warnings, and explicit overrides; metrics does not modify config or historical Tasks. Use spec-manager project readiness critical [--topic <topic>] [--json] for a read-only critical AC readiness report and repair suggestions; it must not auto-generate or insert critical AC. Before enabling adaptive workflow, use spec-manager project workflow preview [--json] for a read-only adoption preview; preview does not write config, migrate historical Tasks, or act as an enable gate.
  • quick remains a restricted lightweight exception and does not create the full L1/L2/L3/Task chain.
  • Validate L3 markdown plans with spec-manager spec validate-plan --from-spec <L3-code>.
  • Record execution with spec-manager task step; finish with spec-manager task complete.

Read the full file on GitHub · 31 lines

Changes

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.

  1. 3d ago First seen · 31 lines · 0 tokens per session scan A 893e2308e650

Subscribe to this mod's changes

WINDSURF is an agent published in the GitHub repository loki-ai-ch/spec-manager (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 558 tokens. A static security scan graded it A with 0 findings. It is 81% identical to AGENTS, differing in 3 lines, and is treated as a copy.

ai-agentsai-codingcli-toolharnesssddspec-driven-development
Related

Other agents, from other repositories

grader

Evaluate expectations against an execution transcript and outputs.

maxritter/pilot-shell · 0 tokens

build-review-codex

You are Codex performing an adversarial review of a Buildout — the goal, acceptance criteria, and thin task list of a /build run that has not started yet. This is not a code diff and not a spec plan. Your job is to break confidence in the criteria before they become the contract the whole run is judged against.

maxritter/pilot-shell · 0 tokens

planner

Drafts the execution Plan (plan.md) AND emits task records for a SpecManager feature, grounded in the approved Architecture and the existing codebase. Plans MUST be organised into phases with Fibonacci-scored tasks ≤3.

joanseg/specmanager · 46 tokens

walkthrough-writer

Writes a per-phase Walkthrough document for a SpecManager feature, or — in phase: "final" mode — a feature-level roll-up that links each phase walkthrough.

joanseg/specmanager · 40 tokens

architect

Drafts an Architecture document for a SpecManager feature, grounded in the approved PRD AND the existing codebase. Reads repo source/conventions before writing.

joanseg/specmanager · 33 tokens

prd-writer

Drafts a PRD (Product Requirements Document) for a SpecManager feature. Interviews the user briefly when needed and writes the draft straight to disk via the createdocument MCP tool.

joanseg/specmanager · 40 tokens