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/fossasia/eventyay/code-reviewnpx skills add fossasia/eventyay --skill code-reviewgit clone --depth 1 https://github.com/fossasia/eventyayWrote 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/fossasia/eventyay/code-review)<a href="https://agentmods.dev/skills/fossasia/eventyay/code-review"><img src="https://agentmods.dev/badge/skills/fossasia/eventyay/code-review.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.00019 | $0.00878 |
| Opus 5 | $0.00010 | $0.00439 |
| Sonnet 5 | $0.00004 | $0.00176 |
| Haiku 4.5 | $0.00002 | $0.00088 |
Grade A, and why
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 4d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Protocol
This skill provides the standard operating procedure for AI agents (like GitHub Copilot, Claude, etc.) performing code reviews on the Eventyay repository.
1. Initial Triage & Architecture Checks
Before reviewing specific business logic, strictly enforce these Non-Negotiable Architecture Rules (from AGENTS.md):
- Location Verification: New product code must reside under
app/eventyay/. Tests must reside underapp/tests/. Ensure legacy directories (talk/,video/,src/) are not being actively modified unless requested. - Legacy Namespaces: Reject any new imports or logic using
pretix.*,pretalx.*, orvenueless.*. All new code must use theeventyay.*namespace. - Multi-tenancy (Crucial): Any ORM query accessing event-specific data MUST be wrapped securely with
django_scopes.scope(event=event). Flag missing scopes immediately. - ORM Efficiency: Check for N+1 query vulnerabilities. Ensure
select_relatedandprefetch_relatedare used appropriately. - Error Handling: Reject the use of generic
Exceptionblocks. Code must catch specific exception types. - Imports Structure: Imports must be at the top of the file. Local imports inside functions/methods are strictly for resolving circular dependencies.
- Frontend Hard Rules: No jQuery. No inline scripts in templates. JavaScript must use external ES modules.
2. File-Scoped Standard Enforcement
During the review, you MUST apply the canonical scoped rules based on the files modified in the pull request:
| File Type | Instruction File to Enforce | Key Review Focus |
|---|---|---|
Python (.py) |
.github/instructions/python.instructions.md |
Python 3.12 compatibility, correct typing, proper Django 5.2+ usage, Celery task definitions. |
JavaScript/Vue (.js, .vue) |
.github/instructions/js.instructions.md |
Vue 3 composition API standards, ES modules, strict absence of jQuery. |
Django Templates (.html) |
.github/instructions/django-template.instructions.md |
Structural integrity, template tag correctness, absence of inline JavaScript. |
Jinja Templates (.html, .j2) |
.github/instructions/jinja.instructions.md |
Syntax correctness, context safety and proper escaping. |
| Dockerfile | .github/instructions/dockerfile.instructions.md |
Security, multi-stage build best practices, minimal layer size. |
TOML (.toml) |
.github/instructions/toml.instructions.md |
Syntax validity, uv dependency alignment (app/pyproject.toml). |
| Git Commits | .github/instructions/git-commit.instructions.md |
Conventional commit formatting, descriptive bodies. |
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.
- 4d ago First seen · 49 lines · 19 tokens per session scan A 71d106f8bda1
code-review is a skill published in the GitHub repository fossasia/eventyay (1,655 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 878 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…