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 conorbronsdon/agent-workspace --skill startgit clone --depth 1 https://github.com/conorbronsdon/agent-workspaceWrote 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/conorbronsdon/agent-workspace/start)<a href="https://agentmods.dev/skills/conorbronsdon/agent-workspace/start"><img src="https://agentmods.dev/badge/skills/conorbronsdon/agent-workspace/start/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/conorbronsdon/agent-workspace/start"><img src="https://agentmods.dev/badge/skills/conorbronsdon/agent-workspace/start.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.00035 | $0.00767 |
| Opus 5.5 | $0.00014 | $0.00307 |
| Sonnet 5.5 | $0.00007 | $0.00153 |
| Haiku 4.5 | $0.00003 | $0.00077 |
Grade A, and why
start 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/start — Begin Session
Load your workspace state so the session begins where the last one left off, then give a short briefing. User-timed, so nothing runs ambiently.
Invocation: user-only (disable-model-invocation: true) — you decide when a session
starts, and the flag keeps this skill out of ambient context.
Configuration
Read the optional workspace.yaml at the project root. Below, <state_dir>,
<sessions_dir>, and <task_file> are its resolved values; defaults are state/,
sessions/, and TODO.md. Staleness thresholds come from staleness.current_days (3),
weekly_days (5), blockers_days (7). Full reference: docs/state-model.md.
Instructions
-
Get today's date. Run
date +%Y-%m-%d. Note the day of week. -
Check what changed since last session. If this is a git repository, find the most recent session log in
<sessions_dir>and run:git log --oneline --since="<last session date>"Flag any state or context files modified since the last session — they may hold updates from other sessions or manual edits. If not a git repository (
git rev-parse --git-dirfails), skip this step and continue. -
Load context (read in order):
<state_dir>/current.md— active priorities, open threads<state_dir>/decisions.md— scan the last 5 entries for awareness<state_dir>/weekly-priorities.md— what matters this week<state_dir>/blockers.md— things waiting on dependencies<sessions_dir>/{TODAY}.md— if it exists, you are resuming today
-
Health checks. Flag anything that needs attention; skip silently if all clean:
current.mdolder thanstaleness.current_days— flag itweekly-priorities.mdolder thanstaleness.weekly_days— flag itblockers.mdolder thanstaleness.blockers_days— flag it- Inbox: if the project keeps a drop-zone (e.g.
inbox/) and it holds files, note the count and suggest triaging them - Overdue items: scan
<task_file>for unchecked items with a date that has passed
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 · 67 lines · 35 tokens per session scan A ab847b3851ad
start is a skill published in the GitHub repository conorbronsdon/agent-workspace (2 stars, last pushed 26d ago), licensed MIT. It adds 35 tokens to every session and 767 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-08-31.
Other skills, from other repositories
incident-postmortem
Escribe un postmortem de incidente estructurado o revisión post-incidente. Úsalo cuando se te pida escribir un postmortem, reporte de incidente, revisión P1/P2, reporte de apagón o RCA (análisis de causa raíz). Produce un postmortem sin culpables con cronología, causa raíz, factores contribuyentes, resumen de impacto…
meeting-notes
Estructura y formatea notas de reunión siguiendo las mejores prácticas de PM. Úsalo cuando te pidan crear notas de reunión, formatear notas de discusión, capturar elementos de acción, o documentar decisiones de cualquier tipo de reunión. Produce notas estructuradas con decisiones, elementos de acción (responsable +…
technical-debt-register
Documenta y prioriza un backlog de deuda técnica con impacto empresarial, estimaciones de esfuerzo y estrategia de resolución. Úsalo cuando se te pida auditar deuda técnica, crear un registro de deuda, priorizar deuda técnica para un trimestre, documentar atajos arquitectónicos o construir una hoja de ruta de…
cs-health-scorecard
Construir un cuadro de mando de salud del cliente para una cuenta específica. Úsalo cuando te pidan calificar la salud de la cuenta, evaluar el riesgo de renovación, construir un panel de salud o evaluar la probabilidad de que una cuenta se renueve o expanda. Produce un cuadro de mando de salud estructurado con estado…
stakeholder-update
Crear actualizaciones ejecutivas concisas para stakeholders usando el framework BLUF (Bottom Line Up Front). Usa cuando te pidan escribir una actualización de estado, reporte de progreso, comunicación de proyecto o briefing ejecutivo para liderazgo o stakeholders. Produce una actualización encabezada por BLUF con…
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…