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 GongShichen/LuminaCode --skill process-compliance-reviewgit clone --depth 1 https://github.com/GongShichen/LuminaCodeWrote 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/gongshichen/luminacode/process-compliance-review)<a href="https://agentmods.dev/skills/gongshichen/luminacode/process-compliance-review"><img src="https://agentmods.dev/badge/skills/gongshichen/luminacode/process-compliance-review/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/gongshichen/luminacode/process-compliance-review"><img src="https://agentmods.dev/badge/skills/gongshichen/luminacode/process-compliance-review.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.00017 | $0.00417 |
| Opus 5.5 | $0.00007 | $0.00167 |
| Sonnet 5.5 | $0.00003 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
Process Compliance Review 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 2mo 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
Review the work as a process and evidence audit, not just a code review.
Before reviewing:
- Call
GetTeamContext. - Use
GetTeamContext.contractas the authoritative Team Acceptance Contract. - A standalone
TEAM_ACCEPTANCE_CONTRACT.mdis optional unless the runtime contract lists it inrequired_artifacts.
Required checks:
PRD.mdexists and matches the user request.UX_DESIGN.mdexists and is based on the PRD.BACKEND_PLAN.mdandFRONTEND_PLAN.mdexist and stay within their boundaries.INTERFACE_CONTRACT.mdexists and matches the implementation.INTEGRATION_REPORT.mdexists and proves real component integration.QA_REPORT.mdexists and includes required command evidence.- Implementation files are under the project root.
- The parent working directory is clean for named-project tasks.
- QA and Reviewer gate verdicts are submitted through runtime tools, not only described in prose.
- Reviewer evidence collection stays within expected artifacts. A reviewer-created smoke script or helper file is a process violation unless it was declared as an expected artifact before the review task started.
Blocking findings:
- Missing required document artifact.
- Missing runtime Team Acceptance Contract when the team gates require one.
- A contract document is listed in
required_artifactsbut is absent from both runtime artifacts and disk. - Any unresolved mismatch with an explicit user requirement, PRD acceptance criterion, UX requirement, or runtime contract item.
- Frontend bypasses backend/API/storage contract.
- Backend implements unused or incompatible contract.
- Required verification command is skipped without a specific reason.
- Security, data-loss, correctness, build-breaking, or architecture mismatch risk.
Write review evidence to <project_root>/REVIEW_REPORT.md and call SubmitGateVerdict.
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.
- 2mo ago First seen · 42 lines · 17 tokens per session scan A 3b6de492662a
Process Compliance Review is a skill published in the GitHub repository GongShichen/LuminaCode (9 stars, last pushed 4d ago), licensed Apache-2.0. It adds 17 tokens to every session and 417 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
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.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.