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 Snowflake-Labs/cocoplus --skill sentinel-reportgit clone --depth 1 https://github.com/Snowflake-Labs/cocoplusWrote 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/snowflake-labs/cocoplus/sentinel-report)<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/sentinel-report"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/sentinel-report/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/snowflake-labs/cocoplus/sentinel-report"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/sentinel-report.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.00031 | $0.00527 |
| Opus 5 | $0.00015 | $0.00264 |
| Sonnet 5 | $0.00006 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
sentinel-report 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 5d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objective
You are generating a CocoSentinel evaluation history report for the current project.
Before proceeding, verify that .cocoplus/ exists. If not, output: "CocoPlus is not initialized. Run $pod init first." Then stop.
Step 1 — Collect Evaluation Results
Read all JSON files in .cocoplus/sentinel/ (excluding approvals.jsonl and active-evaluation.lock). Each file is a dimension evaluation result.
If no results exist, output: "No CocoSentinel evaluations found for this project. Run $sentinel <file> to evaluate an artifact." Then stop.
Step 2 — Collect Approvals
Read .cocoplus/sentinel/approvals.jsonl if it exists. Index by artifact_sha.
Step 3 — Build Report
For each evaluation result, cross-reference with approvals:
CocoSentinel Report — <project> — <current date>
Evaluations: <count>
APPROVED: <count>
CONDITIONAL: <count>
BLOCKED: <count>
─────────────────────────────────────────────────────
Artifact SHA Outcome Approved
─────────────────────────────────────────────────────
<artifact_path> <sha8> APPROVED Yes (2026-05-21)
<artifact_path> <sha8> CONDITIONAL Yes (with rationale)
<artifact_path> <sha8> BLOCKED No
─────────────────────────────────────────────────────
Blocked Artifacts (require remediation):
<artifact_path>: FAIL on dimensions [<list>]
Pending Approval:
<artifact_path>: CONDITIONAL — BLOCKING concerns require developer rationale
Anti-Rationalization Table
| Shortcut / Temptation | Why It Fails |
|---|---|
| Skip SHA cross-reference for approvals | Without SHA matching, approvals may reference stale artifact versions — silent false confidence |
| Omit CONDITIONAL artifacts from report | Pending conditionals are the most actionable items — hiding them defeats the report's purpose |
Exit Criteria
- Report displays all evaluations with outcomes and approval status
- Blocked artifacts are highlighted
- Conditional artifacts awaiting approval are listed
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.
- 5d ago First seen · 69 lines · 31 tokens per session scan A f361842fad3d
sentinel-report is a skill published in the GitHub repository Snowflake-Labs/cocoplus (720 stars, last pushed 6d ago), licensed MIT. It adds 31 tokens to every session and 527 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-09-03.
Other skills, from other repositories
cross-review
Verify an implementer's diff with an INDEPENDENT, different-vendor sub-agent (diff plus contract only); turn blocking issues into fix-tasks and loop until clean.
factory-rereview
Re-review a pull request after a push — reconcile the previous review against the new commits, look for new defects the push introduced, then a fresh pass over the whole PR, and finish with a verdict on the PR.
understand-pr
Guided interactive PR review — understand the history and context before forming opinions.
performance-review
Performance-focused code review for identifying bottlenecks and optimization opportunities.
security-review
Security-focused code review checklist for identifying vulnerabilities.
programming-principles
Apply distilled coding principles from 14 classic software books to code review, refactoring, design, and implementation decisions. Do not use for language- or framework-specific tutorials, tool manuals, or tasks already governed by a project's established conventions.