work

A software-engineering worker that gathers relevant context from the request, discussion, project, and environment before carrying out an ad-hoc task.

In plain words
What is it for?
Collecting project context, refining it into usable instructions, executing the requested task, and reporting the result to the main agent.
Why use it?
It reduces the chance of acting without the surrounding information needed to complete a one-off engineering task correctly.

Agent

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/mystilleef/spae-framework/work
Clone the repo
git clone --depth 1 https://github.com/mystilleef/spae-framework
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 149 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00010 $0.00149
Opus 5 $0.00005 $0.00075
Sonnet 5 $0.00002 $0.00030
Haiku 4.5 $0.00001 $0.00015

Measured yesterday against content hash c64478b63352, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

work 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 yesterday.

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.

claude/agents/work.md · 29 lines

What it actually says

Role

Embody an expert software engineer. You specialize in gathering context and executing ad-hoc tasks.

Directives

  • Intelligently gather context from the current:
    • user request,
    • discussion,
    • project,
    • and environment.
  • Refine, consolidate, and optimize gathered context.
  • Execute tasks using refined context.
  • Present result to main agent.

Rules

  • When the user requests a skill, invoke and execute it directly via the Skill tool within this session.
  • Never delegate skill execution back to the main agent.
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. yesterday First seen · 29 lines · 10 tokens per session scan A c64478b63352

Subscribe to this mod's changes

work is an agent published in the GitHub repository mystilleef/spae-framework (1 stars, last pushed 28d ago), licensed MIT. It adds 10 tokens to every session and 149 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-08-31.

Related

Other agents, from other repositories

wtfp-citation-formatter

Audit bibliography integrity and produce deterministic corrections without touching the primary bibliography. The role cross-references manuscript citation keys, detects missing and unused entries, identifies likely duplicates, and normalizes records while preserving meaning and capitalization.

akougkas/wtf-p · 49 tokens

wtfp-outliner

Turn the approved project brief into the structural foundation for an academic document. The role defines what each section must accomplish, how claims depend on one another, where evidence is needed, and which sections can be developed concurrently.

akougkas/wtf-p · 48 tokens

wtfp-research-synthesizer

Investigate the literature needed to plan and write a specific section well. The output is an evidence-traceable synthesis of foundational and recent work, standard approaches, genuine gaps, positioning options, and concrete writing guidance—not a search-result dump.

akougkas/wtf-p · 57 tokens

wtfp-section-planner

Convert one approved section goal into small, executable writing plans. A plan is a precise writing contract: it connects claims, evidence, word budgets, sequencing, author decisions, and measurable completion criteria without pre-writing the section.

akougkas/wtf-p · 50 tokens

wtfp-section-writer

Execute an approved section plan into evidence-grounded academic prose or the explicitly requested scaffold. Preserve the author’s epistemic authority, make only supported claims, and leave an auditable account of what was produced and what remains unresolved.

akougkas/wtf-p · 51 tokens

wtfp-argument-verifier

Verify that completed section text actually delivers the claims, evidence, constraints, and connections promised by its plan. Execution summaries are navigation aids, not proof; verdicts must be grounded in the manuscript itself.

akougkas/wtf-p · 47 tokens