Borrowing it
Nothing to install: this file belongs to JiuTian-dev/SupplyChainCortex. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/JiuTian-dev/SupplyChainCortex/main/.agents/skills/receiving-code-review/SKILL.mdgit clone --depth 1 https://github.com/JiuTian-dev/SupplyChainCortexWrote 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/jiutian-dev/supplychaincortex/receiving-code-review)<a href="https://agentmods.dev/skills/jiutian-dev/supplychaincortex/receiving-code-review"><img src="https://agentmods.dev/badge/skills/jiutian-dev/supplychaincortex/receiving-code-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/jiutian-dev/supplychaincortex/receiving-code-review"><img src="https://agentmods.dev/badge/skills/jiutian-dev/supplychaincortex/receiving-code-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.00038 | $0.01489 |
| Opus 5.5 | $0.00015 | $0.00596 |
| Sonnet 5.5 | $0.00008 | $0.00298 |
| Haiku 4.5 | $0.00004 | $0.00149 |
Grade A, and why
receiving-code-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 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 214 lines · 38 tokens per session scan A c9382e92b8f3
receiving-code-review is a skill published in the GitHub repository JiuTian-dev/SupplyChainCortex (6 stars, last pushed 3mo ago), with no licence file. It adds 38 tokens to every session and 1,489 once invoked, about $0.0002 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-31.
Other skills, from other repositories
review-code
Read code. Understand it. Find issues. Report clearly.
code-review-feedback
Use when receiving code-review feedback, before implementing suggestions — especially when feedback seems unclear or technically questionable. Verify against the codebase and reason about each item instead of agreeing performatively or implementing blindly.
gaia-issue-resolver
End-to-end plan → implement → review pipeline that takes one triaged Gaia issue to a merged-ready PR, with Kill Criteria on the issue and zero follow-up debt. Use when someone says: "resolve this issue", "take #N end-to-end", "work the P0 queue", "fix and ship this issue", "run the resolver", "close out this issue…
review-and-accept
Use when the maintainer reviews an implementation artifact against its task record and decides accepted vs needsrevision, and when the engineer responds to review feedback. Defines GitHub review markers, files-backed reviewstatus, ordered three-lens review, evidence rules, disputed-items protocol, and mandatory triage…
work-unit-audit
Use when every task in a work unit is accepted and the whole unit must be certified by the auditor before closeout, when routing a non-certifying audit report into remediation tasks, or when a re-audit is required because remediation changed the audited artifact. Defines the audit packet, the six audit perspectives…
judge-rubric
Produce structured JudgeRubric outputs for workflow quality gates.