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 flurdy/agent-skills --skill reassessgit clone --depth 1 https://github.com/flurdy/agent-skillsWrote 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/flurdy/agent-skills/reassess)<a href="https://agentmods.dev/skills/flurdy/agent-skills/reassess"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/reassess/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/flurdy/agent-skills/reassess"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/reassess.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.00041 | $0.04270 |
| Opus 5.5 | $0.00016 | $0.01708 |
| Sonnet 5.5 | $0.00008 | $0.00854 |
| Haiku 4.5 | $0.00004 | $0.00427 |
Grade A, and why
reassess 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 4d 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 — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reassess
Step back and ask: does the current plan still serve the project's intended outcomes, given what is actually implemented and unfinished? Returning after an absence is one trigger, not a reason to change direction. No change is a valid result.
/reassess # Current repository only, including at a workspace root
/reassess workspace # Explicitly include a validated workspace and its members
/skill:reassess # Pi; accepts the same workspace argument
Codex can explicitly request this skill by name. Run from the intended repository or workspace root; no arbitrary paths, portfolio scan or apply mode. A request to implement or cull appended to this invocation does not bypass the report-only boundary.
Boundaries and adjacent owners
This is report-only: no source, tracker, artifact or Git mutations. Do not claim work, take over an existing claim, close/supersede/delete anything, archive handoffs, recover worktrees, install dependencies, repair builds, fetch/pull/push/sync, deploy, or write a persistent report. Do not execute project scripts, tests or builds during reassessment, even if the project normally requires them. A separately authorized verification workflow owns those commands. No automatic full review gauntlet, advisor fanout or delegated work.
Read-only remote queries for explicitly in-scope tracker/CI evidence are allowed when available and permitted; Git fetch is not. Never broaden to an organisation or assignee search. Do not repair missing integrations or substitute an untrusted collector. Tool metadata is not a sandbox or execution grant; use available read tools and approved read-only command forms, respecting repository wrappers and harness permissions.
| Owner | Distinction / handoff |
|---|---|
| landscape | Immediate session orientation and resume-or-next, not project direction. |
| backlog-groom | Per-bead prose, labels and lifecycle hygiene, not whether the plan still fits the code. |
| project-brief | Workspace coordination and outcome linkage; reassess also works in one repository and examines implementation assumptions. |
| triage | Approved tracking proposals, with ownership and duplicate checks; not invoked automatically. |
| refine | Sizing an existing outcome; recommend when keep-whole versus split is the question. |
| architect | Substantial redesign or unresolved consequential design; recommend, do not launch. |
What ships with it
3 files 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.
- 4d ago Changed · +1 lines df1c12aea66f
- 7d ago First seen · 301 lines · 41 tokens per session scan A 18769aaae398
reassess is a skill published in the GitHub repository flurdy/agent-skills (9 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 4,270 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-10-13.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…