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 qingye-lab/rootloom --skill project-guidancegit clone --depth 1 https://github.com/qingye-lab/rootloomWrote 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/qingye-lab/rootloom/project-guidance)<a href="https://agentmods.dev/skills/qingye-lab/rootloom/project-guidance"><img src="https://agentmods.dev/badge/skills/qingye-lab/rootloom/project-guidance.svg" alt="Measured on agentmods" 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.00042 | $0.00816 |
| Opus 5 | $0.00021 | $0.00408 |
| Sonnet 5 | $0.00008 | $0.00163 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
project-guidance 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project guidance
Use when the user explicitly asks to persist, refresh, refine, or validate project guidance, or when active repository guidance requests validation. The SessionStart Hook is read-only and never invokes a writer.
Persistent seed, refresh, or refinement requires explicit user intent. The only repository-authored exception is this exact standalone one-time marker in active guidance:
<!-- rootloom:refine-once version=1 -->
It authorizes one refinement of that marked file only. Remove it in the same successful write; validation does not consume it. Natural-language guidance alone never authorizes persistent refinement or any other write.
Route the mode
explicit seed request → seed
explicit refresh request → refresh
explicit refinement or exact marker → refine
user/repository validation request → validate
Resolve this Skill directory and probe first:
python3 <skill-dir>/scripts/seed_project_guidance.py probe --cwd "$PWD"
Seed or refresh
Run the deterministic writer:
python3 <skill-dir>/scripts/seed_project_guidance.py seed --cwd "$PWD"
Run that command without a trust override first. If and only if it returns the exact
untrusted_project skip reason and the user explicitly requested persistence in this
exact repository, retry once with --allow-untrusted. The flag is scoped to that
invocation and does not change Codex or host trust settings. Never infer this override
from a general request to inspect, review, or change code.
It derives observable facts from manifests, lockfiles, package scripts, Make/Just targets, canonical docs, CI, and bounded module discovery. It locks through the Git common directory, checks concurrent edits, writes atomically, and owns only its marked managed block.
Never overwrite an unmarked existing AGENTS.md, AGENTS.override.md, symlinked
guidance, untrusted or disabled projects, temporary paths, vendor/cache trees, or
evidence resolved outside the repository. Respect every script skip reason.
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.
- 7d ago First seen · 104 lines · 42 tokens per session scan A 7e5b810113cb
project-guidance is a skill published in the GitHub repository qingye-lab/rootloom (9 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 816 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
verify-implementation
A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…
frontend-code-review
Trigger when the user requests a review of frontend files (e.g., .tsx, .ts, .js). Support both pending-change reviews and focused file reviews while applying the checklist rules.
review
Use when the user wants code assessed rather than changed — "review PR 88", "is this branch ready to merge?", "look over my changes", "any problems with this diff?", "give me a code review", "what do you think of this PR?", "sanity-check this branch", "ship it?". Applies to a pull request or the current branch when…
fix
PRFlow's code-review reception skill (formerly receiving-code-review), used by the review-and-fix loop and available directly. Use when addressing review feedback already posted on a pull request — verifying findings before applying them — as distinct from /prflow:review-and-fix, which runs the review itself and then…
init
Use when setting up PRFlow in a repo for the first time, or after a plugin update — scaffolds .prflow/config.json from the shipped template (when absent) or backfills newly-added keys into an existing one (preserving your values), and refreshes config.schema.json. Invoke explicitly with /prflow:init.