Borrowing it
Nothing to install: this file belongs to yasuflatland-lf/liferay-dummy-factory. 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/yasuflatland-lf/liferay-dummy-factory/master/.claude/skills/contract-review/SKILL.mdgit clone --depth 1 https://github.com/yasuflatland-lf/liferay-dummy-factoryWrote 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/yasuflatland-lf/liferay-dummy-factory/contract-review)<a href="https://agentmods.dev/skills/yasuflatland-lf/liferay-dummy-factory/contract-review"><img src="https://agentmods.dev/badge/skills/yasuflatland-lf/liferay-dummy-factory/contract-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/yasuflatland-lf/liferay-dummy-factory/contract-review"><img src="https://agentmods.dev/badge/skills/yasuflatland-lf/liferay-dummy-factory/contract-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.00057 | $0.00209 |
| Opus 5.5 | $0.00023 | $0.00084 |
| Sonnet 5.5 | $0.00011 | $0.00042 |
| Haiku 4.5 | $0.00006 | $0.00021 |
Grade A, and why
contract-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 20d 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
Contract review
Review against the checklist in CONTRIBUTING.md (section "Review checklist"), in its order: contract violations come before "does it work". For each finding, cite the file and line and the contract it breaks, linking the doc that defines it.
Also run, and report the result of:
node scripts/check-docs.mjs
./gradlew :modules:liferay-dummy-factory:test
(cd modules/liferay-dummy-factory && yarn test)
./gradlew :integration-test:compileTestGroovy # when specs changed
The integration suite needs Docker and a DXP license; if you cannot run it, say so instead of implying it passed.
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.
- 20d ago First seen · 20 lines · 57 tokens per session scan A b0ecfc6b67df
contract-review is a skill published in the GitHub repository yasuflatland-lf/liferay-dummy-factory (50 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 209 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-10-10.
Other skills, from other repositories
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.
audit-ci
Run and analyze Elements cold CI performance profiles and propose evidence-backed build, test, lint, and dependency-graph improvements. Use whenever asked to profile or benchmark pnpm run ci, rerun ci:profile, create a CI performance audit, compare CI timings, find bottlenecks or the completion path, investigate a CI…