What is project-update?

A workflow for recording a project update as a durable artefact, log entry, and refreshed index entry. It captures decisions, work built or tested, and what was learned.

Use it when reporting progress, a decision, prototype, test result, research finding, or change in project scope.

It makes project history understandable to someone returning months later and avoids repeating approaches that were already tried and rejected.

How superhero-tech/super-brain configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to superhero-tech/super-brain. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/superhero-tech/super-brain/main/.agents/skills/project-update/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/superhero-tech/super-brain

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/superhero-tech/super-brain/project-update/github.svg)](https://agentmods.dev/skills/superhero-tech/super-brain/project-update)

Your own site

<a href="https://agentmods.dev/skills/superhero-tech/super-brain/project-update"><img src="https://agentmods.dev/badge/skills/superhero-tech/super-brain/project-update/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/superhero-tech/super-brain/project-update"><img src="https://agentmods.dev/badge/skills/superhero-tech/super-brain/project-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 953 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00047	$0.00953
Opus 5.5	$0.00019	$0.00381
Sonnet 5.5	$0.00009	$0.00191
Haiku 4.5	$0.00005	$0.00095

Measured 2mo ago against content hash 4ed1b2c6690e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.agents/skills/project-update/SKILL.md · 95 lines

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.

Read the full file on GitHub · 95 lines

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.

2mo ago First seen · 95 lines · 47 tokens per session scan A 4ed1b2c6690e

Subscribe to this mod's changes

project-update is a skill published in the GitHub repository superhero-tech/super-brain (827 stars, last pushed 11d ago), licensed MIT. It adds 47 tokens to every session and 953 once invoked, about $0.0002 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-30.

Project management

project-update next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
project-updatesuperhero-tech/super-brain	Skill	827	11d ago	MIT	A	47	Claude Code, Codex
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	today	MIT	A	103	Claude Code

super-brain: Skill for Claude Code