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 agentmods add skills/pekral/cursor-rules/assignment-compliance-checknpx skills add pekral/cursor-rules --skill assignment-compliance-checkgit clone --depth 1 https://github.com/pekral/cursor-rulesWrote 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/pekral/cursor-rules/assignment-compliance-check)<a href="https://agentmods.dev/skills/pekral/cursor-rules/assignment-compliance-check"><img src="https://agentmods.dev/badge/skills/pekral/cursor-rules/assignment-compliance-check.svg" alt="Measured on agentmods" 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 | $0.00135 | $0.03081 |
| Opus 5 | $0.00068 | $0.01541 |
| Sonnet 5 | $0.00027 | $0.00616 |
| Haiku 4.5 | $0.00014 | $0.00308 |
Grade A, and why
assignment-compliance-check 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Constraints
- Apply
@rules/php/core-standards.mdc - Apply
@rules/git/general.mdc - Apply
@rules/jira/general.mdc - Apply
@rules/reports/general.mdc— the Assignment Compliance markdown block this skill returns to the caller must be written in the language of the linked assignment (Czech issue / JIRA description → Czech block; English → English). Linked-task / PR URLs, author handles, and severity labels follow the rule's Scope clarifications. - The skill must not write any output to disk. It also must not publish anywhere itself — no
gh issue comment, noacli, no JIRA / GitHub MCP write call. The skill returns either the assembled markdown block (on every run that has a linked tracker, including the affirmative report on a clean run) or a skip status (only when no linked tracker is detected) to the calling CR wrapper. The wrapper embeds the block into the single consolidated linked-tracker comment authored by@skills/pr-summary/SKILL.md(one comment per linked issue / JIRA ticket per CR run — see issue #498) only when a block is returned; on the skip status the wrapper embeds nothing and surfaces the status only on the PR comment summary line. - The block must not be embedded into the GitHub PR comment produced by
@skills/code-review/SKILL.md,@skills/code-review-github/SKILL.md, or@skills/code-review-jira/SKILL.md. The PR comment carries technical findings; the linked-tracker comment carries assignment compliance as part of the consolidatedpr-summaryoutput. - The published block must be plain language understandable by a non-technical reader. Include a short example for every criterion that is Not met / Partial / Divergent, and a one-line citation of the requirement for every Met criterion. Do not list open questions for the reviewer — those are out of scope for this skill; only acceptance-criteria status belongs here.
- The published comment must credit the real change author(s) in the
Authorsline — resolved exactly as@skills/pr-summary/SKILL.mdresolves them (git history%an <%ae>+ PRauthor.login+commits[].author.login, JIRA display name when the target is JIRA). Never list the agent / CR identity. When authorship cannot be determined, writeunknown — git history did not yield a recognisable identity. - The published comment must include the
Available behindline whenever the change is reachable only behind a test parameter (feature flag, ENV switch, query-string parameter, request header, A/B variant, admin toggle, allow-listed account). Detect the gating toggle the same way@skills/pr-summary/SKILL.mddoes (scan the diff forconfig('…')/env('…')checks, GrowthBook / Unleash / LaunchDarkly calls, query / header gates, allow-list middleware), name the toggle, and state the value required to reach the change. Omit the line entirely only when the change is reachable unconditionally. - Report every extracted acceptance criterion — Met and unmet alike — scoped to functional / business-logic conformance only. Do not report architecture, code style, test coverage, refactoring opportunities, or any other concern — those are owned by the other review skills.
- Never modify code. This skill is read-only with respect to the codebase.
- Do not expose secrets, internal infrastructure paths, or PII in the comment.
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 · 107 lines · 135 tokens per session scan A 47b1e45d7fd5
assignment-compliance-check is a skill published in the GitHub repository pekral/cursor-rules (6 stars, last pushed 4d ago), licensed MIT. It adds 135 tokens to every session and 3,081 once invoked, about $0.0007 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-31.
Other skills, from other repositories
data-charts-tako
Search and visualize the world's data - get charts, insights, and embeddable knowledge cards for finance, economics, demographics, sports, and more.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
implementation-readiness
Verify BRD-lite, PRD, SRS/FRS, UX, and test prerequisites before implementation starts.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.
render-airdrop-carousel
Assemble a viral iOS "AirDrop" notification-carousel video ad (≈6–8s, 9:16) from a brand line plus 6–16 real product photos — a native AirDrop share-sheet card ("Brand would like to share a · Decline / Accept") springs up and its preview window CYCLES through the products, landing on a range/lineup payoff with an…