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 Mark393295827/third-brain-v7-skills --skill project-flow-opsgit clone --depth 1 https://github.com/Mark393295827/third-brain-v7-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/mark393295827/third-brain-v7-skills/project-flow-ops)<a href="https://agentmods.dev/skills/mark393295827/third-brain-v7-skills/project-flow-ops"><img src="https://agentmods.dev/badge/skills/mark393295827/third-brain-v7-skills/project-flow-ops/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/mark393295827/third-brain-v7-skills/project-flow-ops"><img src="https://agentmods.dev/badge/skills/mark393295827/third-brain-v7-skills/project-flow-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.00928 |
| Opus 5.5 | $0.00012 | $0.00371 |
| Sonnet 5.5 | $0.00006 | $0.00186 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
project-flow-ops 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Flow Ops
<skill_contract> Project objective, tasks, owners, dependencies, budgets, artifacts, current states, and definitions of done. A WIP-limited project state with ranked work, explicit blockers, bounded actions, and verified closure receipts. Every active item has one owner and observable artifact, and completion is backed by its named fresh verification. <non_goals>Hidden WIP, duplicate ownership, status by intuition, backlog accumulation, or completion without evidence.</non_goals>
Maintain a small, inspectable project state machine: BACKLOG -> ACTIVE -> BLOCKED | COMPLETED. Optimize flow and verified outcomes, not task volume.
Usage Template
Provide: project objective, current tasks, owners, dependencies, time budget, artifacts, and definition of done. Optional: prior review receipts.
Workflow
Normalize each item into {id, objective, owner, state, artifact, definition_of_done, budget, dependencies}. Reject duplicate ownership and distinguish waiting from active execution.
<unknowns_gate>
If an active item lacks an owner, artifact, or observable definition of done, return NEEDS_INPUT. Probe the ambiguity with the largest impact on scheduling; do not guess priority from wording alone.
</unknowns_gate>
- Rank work by objective impact, urgency, dependency leverage, and cost of delay.
- Limit
ACTIVEto one or two items per owner. - Decompose the selected item until one bounded action can produce a reviewable artifact.
- For a blocker, record owner, missing condition, evidence, next probe, and review time; move independent work forward.
- Run the verification named in the definition of done.
- Move to
COMPLETEDonly with a fresh receipt; otherwise keepACTIVEorBLOCKED. - At review, remove stale backlog items and state the next constraint.
Check state-transition legality, WIP limits, ownership, artifact existence, and completion evidence. Use an independent check for consequential deliverables. If verification fails, reopen the item with the failure evidence and smallest corrective action.
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 · 95 lines · 31 tokens per session scan A 75e1713995eb
project-flow-ops is a skill published in the GitHub repository Mark393295827/third-brain-v7-skills (141 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 928 once invoked, about $0.0001 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.
Other skills, from other repositories
ara-research-manager
Records research provenance as a post-task epilogue, scanning conversation history at the end of a coding or research session to extract decisions, experiments, dead ends, claims, heuristics, and pivots, and writing them into the ara/ directory with user-vs-AI provenance tags. Use as a session epilogue — never during…
contrib-watch
Watch incoming feedback from outside engineers on your open-source repos: comments, reviews, issues, mentions. Use when you need to find who replied to your pull requests or issues, triage human versus bot responses, and answer within a day with evidence.
peer-onboard
A procedure for bringing an outside lead or peer into a shared working setup, including their contact space, records, previous conversations, and ongoing session.
retro-lost
Run a retrospective for an abandoned agent session (untouched for over 24 hours, never closed with a retro): rebuild context cold from the transcript, list what was built, sort Keep/Drop/Try and file the durable parts. Use from a nightly routine or on demand. Triggers: /retro-lost, retro for an abandoned session.
issue-match
Measure a target repository's queue and find a live open issue the contribution would close, before opening a pull request there. Reports how many PRs are open, how many of the last N closed ones were actually merged, and which issue to attach to, because a cold PR into a dead queue is a wasted artifact. Triggers…
outbound-gate
Gate for any outbound message before it leaves: pull request or issue comment, DM, invite, post, email. Use before sending to check facts, tone, platform rules, registry status and AI-slop, and to block text that fails.