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 SpillwaveSolutions/agent-brain --skill gsd-validate-phasegit clone --depth 1 https://github.com/SpillwaveSolutions/agent-brainWrote 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/spillwavesolutions/agent-brain/gsd-validate-phase)<a href="https://agentmods.dev/skills/spillwavesolutions/agent-brain/gsd-validate-phase"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/agent-brain/gsd-validate-phase/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/spillwavesolutions/agent-brain/gsd-validate-phase"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/agent-brain/gsd-validate-phase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00019 | $0.00661 |
| Opus 5.5 | $0.00008 | $0.00264 |
| Sonnet 5.5 | $0.00004 | $0.00132 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
gsd-validate-phase 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- gsd-validate-phase — 88% identical, 4 lines differ
- gsd-new-workspace — 80% identical, 47 lines differ
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<codex_skill_adapter>
A. Skill Invocation
- This skill is invoked by mentioning
$gsd-validate-phase. - Treat all user text after
$gsd-validate-phaseas{{GSD_ARGS}}. - If no arguments are present, treat
{{GSD_ARGS}}as empty.
B. AskUserQuestion → request_user_input Mapping
GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:
Parameter mapping:
header→headerquestion→question- Options formatted as
"Label" — description→{label: "Label", description: "description"} - Generate
idfrom header: lowercase, replace spaces with underscores
Batched calls:
AskUserQuestion([q1, q2])→ singlerequest_user_inputwith multiple entries inquestions[]
Multi-select workaround:
- Codex has no
multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.
Execute mode fallback:
- When
request_user_inputis rejected (Execute mode), present a plain-text numbered list and pick a reasonable default.
C. Task() → spawn_agent Mapping
GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:
Direct mapping:
Task(subagent_type="X", prompt="Y")→spawn_agent(agent_type="X", message="Y")Task(model="...")→ omit (Codex uses per-role config, not inline model selection)fork_context: falseby default — GSD agents load their own context via<files_to_read>blocks
Parallel fan-out:
- Spawn multiple agents → collect agent IDs →
wait(ids)for all to complete
Result parsing:
- Look for structured markers in agent output:
CHECKPOINT,PLAN COMPLETE,SUMMARY, etc. close_agent(id)after collecting results from each agent </codex_skill_adapter>
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 · 69 lines · 19 tokens per session scan A 74311c5a55bc
gsd-validate-phase is a skill published in the GitHub repository SpillwaveSolutions/agent-brain (119 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 661 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-05.
Other skills, from other repositories
test-result-feedback
Close the acceptance loop for a tested change — consume the apc test TierResult, map EACH acceptance criterion to a pass/fail outcome from structured fields (never chat text), attach an evidence ref, and write it back to the task. A SUT red is a finding, never softened to green.
ov-kanban
Work through tasks on a kanban board stored in OpenViking (viking://agent/kanban/ /, one markdown file per task). Use when the user says "ov kanban", "kanban", "看板", asks to put a task on the board, hand off the current work, continue a task another agent started, or run an unattended task loop. A board holds many…
nightly-close-parity
Unique project-local fire verb for the seven-leg nightly close-parity pass. Proves and loads the canonical top-level skill.
test-plan
Build a test plan when a new Epic is created. Pulls epic details and linked stories from Jira, analyzes scope, and produces a test plan covering strategy, automation gap analysis, success criteria, environment needs, and risks. Output goes to Confluence and local test knowledge base. Use when: "test plan", "plan tests…
review-ticket
Review a Jira ticket during backlog grooming or refinement. Audits the ticket for testability, AC completeness, missing edge cases, and potential blockers. Outputs a structured review the SDT can bring to the grooming session. Use when: "review this ticket", "check ACs", "testability review", "grooming". Do NOT use…
workflow-qa
A quality-assurance procedure for testing Workflow documents and features in their real online environment. QA means checking whether software behaves as expected and recording evidence.