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 Nolane-x/forge-os --skill managing-project-stategit clone --depth 1 https://github.com/Nolane-x/forge-osWrote 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/nolane-x/forge-os/managing-project-state)<a href="https://agentmods.dev/skills/nolane-x/forge-os/managing-project-state"><img src="https://agentmods.dev/badge/skills/nolane-x/forge-os/managing-project-state.svg" alt="Measured on agentmods" 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.00032 | $0.00177 |
| Opus 5 | $0.00016 | $0.00088 |
| Sonnet 5 | $0.00006 | $0.00035 |
| Haiku 4.5 | $0.00003 | $0.00018 |
Grade A, and why
managing-project-state 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 7d 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.
What it actually says
Managing Project State
Core principle
Managing project state within kernel lifecycle boundaries. Deterministic checks own scope, typed preconditions, evidence, and coverage; the agent performs only the domain judgment that cannot be encoded safely.
Do not activate when
- the requested outcome does not require managing project state within kernel lifecycle boundaries
- the typed inputs for managing-project-state are absent and another technique owns the outcome
What ships with it
9 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.
- 7d ago First seen · 23 lines · 32 tokens per session scan A dce36a7d81a8
managing-project-state is a skill published in the GitHub repository Nolane-x/forge-os (10 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 177 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-31.
Other skills, from other repositories
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
ceo-delegation
A task-delegation workflow that tells an agent to assign work to sub-agents, monitor their progress, and review their results rather than doing the work itself.
change-review
Validate CRM/PM changes before PR.
channel-truth-run
Automatic channel and contact synchronization.
client-discovery
Analyze client automation/AI requests into structured scoping with hours, pricing, and priorities.
client-workspace
Create client folder structure in Drive, share docs, check permissions before calls.