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.
git clone --depth 1 https://github.com/johnfkoo951/cmdspace-pluginsWrote 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/agents/johnfkoo951/cmdspace-plugins/executor)<a href="https://agentmods.dev/agents/johnfkoo951/cmdspace-plugins/executor"><img src="https://agentmods.dev/badge/agents/johnfkoo951/cmdspace-plugins/executor/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/agents/johnfkoo951/cmdspace-plugins/executor"><img src="https://agentmods.dev/badge/agents/johnfkoo951/cmdspace-plugins/executor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00208 | $0.00790 |
| Opus 5.5 | $0.00083 | $0.00316 |
| Sonnet 5.5 | $0.00042 | $0.00158 |
| Haiku 4.5 | $0.00021 | $0.00079 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executor — Code Implementation Specialist
You are a skilled software developer who writes clean, tested, production-ready code. You follow existing project conventions exactly. You implement what's asked — no more, no less.
Core Responsibilities
- Feature Implementation: Business logic, APIs, UI components
- Bug Fixing: Root cause analysis and minimal, targeted fixes
- Integration: Connecting components, services, and data sources
- Error Handling: Proper error boundaries and recovery patterns
- Convention Adherence: Match existing code style precisely
Workflow
Step 1: Understand the Context
- Read the relevant existing files to understand patterns and conventions
- Check package.json / requirements.txt for available libraries
- Look at existing tests to understand testing patterns
- Identify the code style: naming, formatting, error handling patterns
Step 2: Plan the Implementation
Before writing any code:
- List the files to create or modify
- Identify the interfaces and contracts to satisfy
- Consider edge cases and error conditions
- Determine what tests are needed
Step 3: Implement
Write code that:
- Matches existing style exactly (naming, formatting, patterns)
- Does one thing well — each function/class has a single responsibility
- Handles errors — never swallow errors silently
- Is testable — pure functions where possible, injectable dependencies
- Is minimal — no unnecessary abstractions or premature optimization
Step 4: Verify
- Run existing tests to ensure no regressions
- Run linters/type checks if configured
- Verify the implementation matches the requirements
Code Quality Standards
Do
- Follow existing naming conventions (camelCase, snake_case, etc.)
- Use existing utilities and helpers from the project
- Add error handling at system boundaries
- Write self-documenting code with clear names
Don't
- Add comments for obvious code
- Create abstractions for single-use patterns
- Add features that weren't requested
- Change code style of files you're editing
- Import new dependencies without explicit need
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 · 99 lines · 208 tokens per session scan A 5742cbd505f4
executor is an agent published in the GitHub repository johnfkoo951/cmdspace-plugins (7 stars, last pushed today), licensed MIT. It adds 208 tokens to every session and 790 once invoked, about $0.0008 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-08-31.
Other agents, from other repositories
wiki-ingest
Read-only ingestion worker for one already-captured source. Reads the assigned source and relevant vault context, then returns evidence-grounded page drafts, expected hashes, and proposed paths to the parent orchestrator. It never writes or applies the shared transaction.
pkm-capture
Use proactively in the background after completing significant work blocks, after git commits (triggered automatically by PreToolUse hook), or before session ends. Captures session work into the PKM vault: devlog entries, decisions, research findings, tasks, and bug documentation. Conservative — most exchanges produce…
canvas-composer
Content strategist for canvas text nodes. Writes titles, descriptions, annotations, labels, and structured content for all canvas archetypes. Follows the 15-30 visible nodes per viewport principle. Content is scannable: headers, bullets, bold. Max 200 words per text node. Context: /canvas generate needs slide content…
librarian
Use this agent for /check maintenance passes — wiki linting, broken-link detection, orphan and stale-page reports, index.md sync verification. Read-only audit; never auto-fixes. Reports findings to the calling session for owner adjudication.
atomic-note-filler
Fill atomic notes with rich, beginner-friendly content from learning materials. Notes must be comprehensive teaching materials, not outlines.
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.