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 skills/superhero-tech/super-brain/project-updatenpx skills add superhero-tech/super-brain --skill project-updategit clone --depth 1 https://github.com/superhero-tech/super-brainWhat 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.00047 | $0.00953 |
| Opus 5 | $0.00023 | $0.00477 |
| Sonnet 5 | $0.00009 | $0.00191 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
project-update 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 3d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Update
Turn "here is what happened this week" into project state someone can pick up cold in three months.
Write every file in the language the human is using.
How to invoke
- "I have an update", "here is what happened", "update the project"
- The human reports a decision, a prototype, a test result or a piece of research
- The scope of a project has moved
How it works
1. Orient before you write
Read, in this order:
3-Projects/index.md- which projects exist and which one this is about<project>/brief.md- what it was meant to be<project>/rules.md- constraints that override your defaults here- The top five entries of
<project>/log.md- what it has actually become
The brief and the log answer different questions. Skipping the log is how you give advice that was already tried and rejected two weeks ago.
If the human has not said which project, ask. Guessing from the topic puts work in the wrong folder.
2. Ask for what is missing
Most updates arrive as one sentence. The three questions that turn it into something durable:
- What did you decide?
- What did you build or test?
- What did you learn?
Ask only about the gaps. An update that already says what changed and why does not need an interview.
3. Write the artefact
Route by what actually happened:
| What happened | Where it goes |
|---|---|
| A decision | <project>/decisions/, using 6-Templates/decision-record.md |
| Something built | <project>/prototypes/ - link, screenshots, spec |
| A result or a learning | <project>/analyses/ |
| Interviews, data, hypotheses | <project>/discovery/ |
File names start with the date: 2026-03-14-drop-templates.md.
Everything stays inside the project folder. Project work does not go to 9-Outputs/ or the vault root.
4. Log it
Append an entry to <project>/log.md, newest at the top. The entry format and the list of valid types are in 3-Projects/README.md - read it if you have not this session.
Two fields carry the weight: what changed and why. An entry without a why is a changelog, and a changelog does not help anyone decide anything later. Point Files at the artefact you just wrote; the log summarises, it never becomes the artefact.
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.
- 3d ago First seen · 95 lines · 47 tokens per session scan A 4ed1b2c6690e
project-update is a skill published in the GitHub repository superhero-tech/super-brain (110 stars, last pushed 8d ago), licensed MIT. It adds 47 tokens to every session and 953 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…