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 agentmods add skills/static-var/keystone/project-auditnpx skills add static-var/Keystone --skill project-auditgit clone --depth 1 https://github.com/static-var/KeystoneWhat 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 | $0.00047 | $0.02450 |
| Opus 5 | $0.00023 | $0.01225 |
| Sonnet 5 | $0.00009 | $0.00490 |
| Haiku 4.5 | $0.00005 | $0.00245 |
Grade A, and why
project-audit 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 2d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Audit
Core principle
Project Audit is a read-only, whole-project condition scan. It turns repository evidence into mechanical findings about system drift, fragility, and maintenance risk; it does not repair, refactor, update, or reconfigure anything by default.
Project Audit answers “what is the condition of this project or subsystem?” Change Review answers “is this specific change acceptable?” If the task centers on a PR/diff/patch, use change-review; if it centers on repo-wide readiness, drift, tooling, docs, tests, releases, or operational condition, use project-audit.
Load when
Load when the user asks for a whole-system condition scan of a concrete software repository or product subsystem: project health, release readiness, tooling/CI drift, dependency/config condition, maintenance risk, architecture smells, docs-vs-reality, test health, packaging, or instruction drift.
At entry, use the full Keystone path when repository or subsystem evidence must support a project-level health verdict. Handle general risk questions, personal health checks, and narrow standalone inspections directly. Explicit invocation selects the full Project Audit behavior.
Not for
- Fixing issues found during the audit.
- Reviewing a specific change, PR, patch, or commit; use
change-review. - Tracing a specific failure to root cause; use
root-cause-analysis. - Shipping a completed branch; use
shipping. - Designing new product behavior; use
product-planning. - Context Survey briefs about a narrow question; use
context-survey.
Outcome contract
Deliver a project audit report where every finding maps:
finding -> evidence -> impact -> confidence -> next Keystone module
The report must include:
- audit scope and evidence inspected;
- concrete checklist status for tooling/CI drift, docs-vs-reality, config/env rot, dependency health, test health/flakiness, package/release health, and instruction/skill drift;
- risks ranked by severity and confidence using the Project Audit priority rubric;
- checks not run and why;
- explicit no-fix confirmation unless repairs were requested.
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.
- 2d ago First seen · 140 lines · 47 tokens per session scan A 225b0a68358c
project-audit is a skill published in the GitHub repository static-var/Keystone (4 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 2,450 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
criticism-self-criticism
触发：当一项工作已经完成、进入阶段验收、收到批评反馈，或反复出现同类错误需要系统纠偏时调用；常见信号包括 review、audit、retrospective、quality check、纠错与复盘。 English: Trigger after delivery or at a review checkpoint when quality must be examined honestly and errors must be corrected without defensiveness. Use this skill for structured self-review, feedback processing, and…
mass-line
触发：当你需要收集多方意见、把零散反馈整合成可执行方案，或把方案带回真实使用者/执行者验证时调用；常见信号包括 stakeholder input、user feedback、意见汇总、对齐与验证。 English: Trigger when input must be gathered from many people, synthesized into a clearer plan, and returned to the affected users or executors for validation. Use this skill for a collect-synthesize-validate loop.
workflows
触发：当你面临的任务明显需要多个思想武器协作时调用；常见信号包括：从零启动新项目、攻坚复杂疑难问题、对已有方案进行迭代优化。此 skill 提供标准化的跨 skill 工作流组合，解决"应该先用哪个 skill、怎么衔接"的问题。 English: Trigger when a task clearly requires multiple skills in sequence. Use this skill to select a standard workflow that chains skills together, defines data handoff between steps, and specifies…
concentrate-forces
触发：当多个任务同时争夺时间、注意力、算力或预算，必须确定主攻方向并停止分散用力时调用；常见信号包括优先级过多、资源紧张、推进分散、需要决定先做什么。 English: Trigger when limited resources are being split across too many tasks and one main target must be chosen. Use this skill to concentrate effort, sequence work decisively, and finish a meaningful breakthrough before expanding.
investigation-first
触发：当你准备下判断、做决策或提出建议，但事实、上下文或一手信息还不充分时优先调用；常见信号包括 unknowns、信息缺口、证据不足、领域陌生、需要先摸清现状。 English: Trigger before making claims or decisions when context is incomplete, evidence is weak, or the domain is unfamiliar. Use this skill to investigate first, gather firsthand facts, and let reality shape the conclusion.
overall-planning
触发：当你需要在多个目标、利益方或相互制约的指标之间做动态平衡时调用；常见信号包括 trade-offs、目标冲突、系统性约束、优化一项会伤害另一项。 English: Trigger when several important goals must be advanced together and optimizing one dimension can damage another. Use this skill to map the key relationships, avoid one-sided decisions, and balance the system as a whole.