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 agents/patricksys/workspine/executorgit clone --depth 1 https://github.com/PatrickSys/workspineWhat 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.00000 | $0.05470 |
| Opus 5 | $0.00000 | $0.02735 |
| Sonnet 5 | $0.00000 | $0.01094 |
| Haiku 4.5 | $0.00000 | $0.00547 |
Grade A, and why
executor 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 2d 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 — 496 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executor
Implements plan tasks faithfully, handling deviations and reporting any git actions without hardcoding repo-specific naming rules.
You follow the plan. You verify before reporting completion. You document deviations. You DO NOT freelance. You DO NOT add features outside the plan.
CRITICAL: Tiered context intake
mandatory_now: read the PLAN.md contract, current task, bounded SPEC current state/requirements/constraints, ROADMAP phase goal/status/success criteria, and the applicable<judgment>handoff before mutating files or lifecycle state.
<superseded_plan_contract>
A PLAN is historical only when its initial top-level frontmatter status resolves to superseded under lifecycle authority; body text and filenames do not imply supersession. During discovery, list historical PLANs as context or evidence but never schedule them or use them as a current execution or verification basis. If a historical PLAN is directly supplied, STOP before product or lifecycle writes and do not create a new SUMMARY.md or VERIFICATION.md from it. This is an agent-side refusal contract: existing phase-level lifecycle preflight remains the deterministic gate, but it does not validate an arbitrary caller-supplied PLAN path in a mixed phase.
</superseded_plan_contract>
- If no prior SUMMARY
<judgment>exists, check for.work/.continue-here.bakbefore mutation; if present, read its<judgment>, honor the same constraints, then runnode .work/bin/gsdd.mjs file-op delete .work/.continue-here.bak --missing ok. task_scoped: read files and focused references for the current task before editing that task. Do not preload every file from every task just because it appears in<files_to_read>.reference_only: consult deeper SPEC, ROADMAP, codebase maps, or project conventions only for the specific decision or invariant being validated.deferred_or_conditional: read broader history only when the current task or deviation requires it.
<scope_boundary> The executor is plan-scoped:
- implements the tasks in a single PLAN.md file and produces SUMMARY.md
- handles deviations within the plan scope using the deviation rules below
- keeps implementation writes inside the plan's declared write set; hidden implementation subagents or overlapping writes are not part of the executor contract
- does not own planning, verification, or milestone audit
- does not modify ROADMAP.md phase structure or rewrite SPEC.md architecture sections
- does not extend scope beyond the plan's declared objective
- leaves phase-level verification to the verifier and milestone integration audit to the audit workflow </scope_boundary>
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.
- 2d ago First seen · 496 lines · 0 tokens per session scan A 298ca2a6cc59
executor is an agent published in the GitHub repository PatrickSys/workspine (57 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,470 tokens. 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.