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 brunob54/superpowers-orchestrator --skill workloggit clone --depth 1 https://github.com/brunob54/superpowers-orchestratorWrote 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/brunob54/superpowers-orchestrator/worklog)<a href="https://agentmods.dev/skills/brunob54/superpowers-orchestrator/worklog"><img src="https://agentmods.dev/badge/skills/brunob54/superpowers-orchestrator/worklog/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/brunob54/superpowers-orchestrator/worklog"><img src="https://agentmods.dev/badge/skills/brunob54/superpowers-orchestrator/worklog.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.00120 | $0.05530 |
| Opus 5.5 | $0.00048 | $0.02212 |
| Sonnet 5.5 | $0.00024 | $0.01106 |
| Haiku 4.5 | $0.00012 | $0.00553 |
Grade A, and why
worklog 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 — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work log
A work log is one Markdown document per piece of work that has several parts
and lasts many sessions, for example four groups of tests that are refactored
one group after the other. It lives at docs/worklogs/<slug>.md under the
root, and git tracks it. It carries its own update rules in its section
How to maintain this document, so a session can maintain it without this
skill. This skill creates a work log, runs a full update, and closes it. This
skill never commits: the work log goes into the next commit that the user
requests.
Argument given by the user (may be empty): $ARGUMENTS
Terms
- Slug rule: a slug matches
^[a-z0-9]+(-[a-z0-9]+)*$(lowercase ASCII letters, digits, single hyphens), has at most 40 characters, and is none of the three command wordsnew,updateandclose. The file name is the authority for the slug; theslug=field of line 1 repeats it for a human reader. - Root: the output of
git rev-parse --show-toplevel; in a project that is not a git repository, the folder of the shell at the moment of the command. Everydocs/worklogs/path in this skill is relative to the root. - Active: a work log whose line 1 starts with
<!-- Work log: status=active. - Today: the output of
date +%F, run with the Bash tool. <skill-dir>: this skill's base directory. A path underskills/exists only inside the plugin's own repository, never in a user's project.
Commands and arguments
Grammar: /worklog [new|update|close] [<slug>]
The first word is always read as a command word, never as a slug. When the
user types /worklog with no first word, the command is update; the test
at the end of this section decides whether the user typed the command. Any
other first word, and a command word
given as a slug (for example /worklog new close), stops with the usage text and writes nothing. More than one word after the command word also stops with the usage text and writes nothing. The usage text is the grammar line and one line per command:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 367 lines · 120 tokens per session scan A 022e5f0fe7b9
worklog is a skill published in the GitHub repository brunob54/superpowers-orchestrator (3 stars, last pushed yesterday), licensed MIT. It adds 120 tokens to every session and 5,530 once invoked, about $0.0005 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-09-23.
Other skills, from other repositories
sessions
Use when the user wants to see active Tandem sessions, inspect session details, clean orphaned sessions, or understand which sessions share a project.
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
promote-idea
Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".
customer-onboarding-and-implementation
Takes a new customer from signature to working — setting a definition of live that both sides agreed before the contract was signed, planning and staffing the implementation, running data migration and integration realistically, training the people who will actually use it, and handing over to the ongoing…
vendor-management
Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or…
ledger
OPS on-demand: This skill should be used when the user asks to "ops ledger", "what did we handle", or…