gsd-manager

gsd-manager is a skill for Codex from SpillwaveSolutions/agent-brain. It costs 14 tokens per session (795 once invoked), scanned A, original, MIT.

An interactive command centre for managing several project phases from one terminal. It supports workstreams such as creating, switching, checking, completing, and resuming phases.

In plain words
What is it for?
It is for coordinating project phases, checking progress, moving between workstreams, and resuming unfinished work.
Why use it?
It gives multi-phase work a single place to track what is active and what remains to be done.

Skill for Codex

Written for Codex: installed under .codex/. Also seen: names the AskUserQuestion tool; mentions Claude Code; mentions Codex.

Good fit It is for coordinating project phases, checking progress, moving between workstreams, and resuming unfinished work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/spillwavesolutions/agent-brain/gsd-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.

Any agent
npx skills add SpillwaveSolutions/agent-brain --skill gsd-manager
Clone the repo
git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain

Made for: Codex.

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 gsd-manager

README.md
[![agentmods](https://agentmods.dev/badge/skills/spillwavesolutions/agent-brain/gsd-manager/github.svg)](https://agentmods.dev/skills/spillwavesolutions/agent-brain/gsd-manager)
Your own site
<a href="https://agentmods.dev/skills/spillwavesolutions/agent-brain/gsd-manager"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/agent-brain/gsd-manager/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.

agentmods 80×15 button for gsd-manager

Your own site · 80×15
<a href="https://agentmods.dev/skills/spillwavesolutions/agent-brain/gsd-manager"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/agent-brain/gsd-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 795 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found 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.1 $0.00014 $0.00795
Opus 5 $0.00007 $0.00398
Sonnet 5 $0.00003 $0.00159
Haiku 4.5 $0.00001 $0.00080

Measured 4d ago against content hash 8bc7902995ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

gsd-manager 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 4d 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.

.codex/skills/gsd-manager/SKILL.md · 75 lines

How it starts

The opening of the file, as written. The whole thing — 75 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-manager.
  • Treat all user text after $gsd-manager as {{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:

  • headerheader
  • questionquestion
  • Options formatted as "Label" — description{label: "Label", description: "description"}
  • Generate id from header: lowercase, replace spaces with underscores

Batched calls:

  • AskUserQuestion([q1, q2]) → single request_user_input with multiple entries in questions[]

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_input is 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: false by 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>

Read the full file on GitHub · 75 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. 4d ago First seen · 75 lines · 14 tokens per session scan A 8bc7902995ae

Subscribe to this mod's changes

gsd-manager is a skill published in the GitHub repository SpillwaveSolutions/agent-brain (118 stars, last pushed 5d ago), licensed MIT. It adds 14 tokens to every session and 795 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-09-05.

Related

Other skills, from other repositories

mempalace-task

Create, hand off, claim, execute, and close agent tasks through the MemPalace logstream. Use when the user wants to delegate work, prepare a ready-to-paste task for another agent, receive a MemPalace task id, or explicitly launch a supported headless agent in controlled mode.

MemPalace/mempalace · 67 tokens

install-openviking-memory

Install and configure the OpenViking long-term memory plugin for OpenClaw via natural conversation. Once installed, the plugin automatically captures facts from chats and recalls relevant context before each reply (auto-capture + auto-recall, cross-session). Covers prerequisites, install through OpenClaw's plugin…

volcengine/OpenViking · 191 tokens

daily-report

Compile timestamped conversation logs, agent sessions, IM messages, collaborative documents, meeting notes, task records, and similar OpenViking materials into concise, evidence-grounded daily reports. Use with ov compile when the user asks for a daily work report, end-of-day digest, 日报, or reports for one or more…

volcengine/OpenViking · 88 tokens

knowledge-distillation

Compile one or more OpenViking knowledge bases or document collections into topic-organized, evidence-grounded high-level knowledge, including cross-source findings, trends, changes, drivers, comparisons, implications, and uncertainties. Use with ov compile when the user asks to distill or synthesize a knowledge base…

volcengine/OpenViking · 89 tokens

experience_loader

Load relevant OpenViking experience memories via case-linked experience candidates before solving a task.

volcengine/OpenViking · 20 tokens

tmux

Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.

volcengine/OpenViking · 22 tokens