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 it235/multica-best-practices --skill multica-review-backendgit clone --depth 1 https://github.com/it235/multica-best-practicesWrote 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/it235/multica-best-practices/multica-review-backend)<a href="https://agentmods.dev/skills/it235/multica-best-practices/multica-review-backend"><img src="https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-review-backend/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/it235/multica-best-practices/multica-review-backend"><img src="https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-review-backend.svg" alt="Reviewed on agentmods" width="80" 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.00055 | $0.00452 |
| Opus 5 | $0.00028 | $0.00226 |
| Sonnet 5 | $0.00011 | $0.00090 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade A, and why
multica-review-backend 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 yesterday.
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
Backend Implementation Professional Review (BackendReviewer)
Structured professional review framework for backend implementation artifacts (API contract + implementation). Called by BackendReviewer; reviews the links BackendDev returns via multica-artifact-backend and code-class skill (Apifox / changed-file list), plus the architecture design ref Leader passes.
When to use
- BackendReviewer receives a "review backend implementation" dispatch from Leader.
- Entering a re-review round after implementation changes (check previous round's fix list item by item).
Review dimensions (conclusion per item)
- Contract quality: field naming, status codes, error model, versioning clear & self-consistent.
- Design fit: implementation aligned with Architect plan, deviations explained.
- Error handling: exception branches, timeouts, idempotency, boundaries covered.
- Unit-test sufficiency: key paths, boundaries, exception branches covered; no无效的 tests (mark & block).
- Acceptance mapping: implementation truly satisfies every AC-.
Output format
【Backend Review】<change link>
Conclusion: PASS / FAIL
Blocking items (required on FAIL, each: rationale / involved point / fix direction):
- ...
Suggestions (non-blocking):
- ...
Previous fix-list check (re-review): resolved X / unresolved Y
Round: N / 3
Conclusion + fix list reported to Leader; don't modify code or notify BackendDev yourself.
Boundaries
- Review only backend contract & implementation, unit tests; not frontend, UI, requirements, architecture design itself, or test cases.
- Don't replace Leader's generic gate (multica-verification skill).
- Architecture-level disagreement goes to ArchReviewer; you own implementation-layer quality.
- Still FAIL at round 3 → mark "escalate to human", hand to Leader, stop looping.
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.
- yesterday Changed 63df724cca7d
- 12d ago First seen · 39 lines · 55 tokens per session scan A 94f4379c0c3f
multica-review-backend is a skill published in the GitHub repository it235/multica-best-practices (119 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 452 once invoked, about $0.0003 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-30.
Other skills, from other repositories
platform-apex-generate
Primary Apex authoring skill for class generation, refactoring, and review. ALWAYS ACTIVATE when the user mentions Apex, .cls, triggers, or asks to create/refactor a class (service, selector, domain, batch, queueable, schedulable, invocable, DTO, utility, interface, abstract, exception, REST resource). Use this skill…
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
api-contract-review
Use when auditing CloudBase cloud API wrappers, MCP tools, generated action metadata, or related docs for outdated or incorrect action names, parameters, casing, request shapes, or missing contract tests, especially during periodic quality review or before preparing corrective PRs.
principle-model-the-domain
Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.
api-reviewer
A review of an API contract, the agreed description of how software systems exchange requests, responses, events, or files.