Eventyay is an open-source platform for managing events, including ticket sales and registration, speaker submissions, session schedules, videos, check-ins, badges, exhibitions, and organiser administration. Event organisers use it to run both in-person and online event workflows.
Borrowing it
Nothing to install: this file belongs to fossasia/eventyay. 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/fossasia/eventyay/dev/.agents/skills/repo-navigation/SKILL.mdgit 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/repo-navigation)<a href="https://agentmods.dev/skills/fossasia/eventyay/repo-navigation"><img src="https://agentmods.dev/badge/skills/fossasia/eventyay/repo-navigation/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/fossasia/eventyay/repo-navigation"><img src="https://agentmods.dev/badge/skills/fossasia/eventyay/repo-navigation.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.00010 | $0.00727 |
| Opus 5 | $0.00005 | $0.00364 |
| Sonnet 5 | $0.00002 | $0.00145 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade A, and why
repo-navigation 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 13d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Repository Navigation
Top-level Layout
.
├── app/ # Main Django application
├── deployment/ # Infrastructure and deployment configs
├── doc/ # Project documentation
├── .github/instructions/ # File-scoped AI coding guidance
├── .agents/skills/ # AI agent skill files (this directory)
├── agents.md # Canonical AI agent policy
├── docker-compose.yml # Docker Compose for local/dev environment
├── DEPLOYMENT.md # Production deployment walkthrough
├── CONTRIBUTING.md # Contributor guidelines
└── README.rst # Project overview
Application Root: app/
app/
├── eventyay/ # Core Django application package
├── tests/ # Test suite
├── pyproject.toml # Project metadata and dependencies
└── manage.py # Django management entry point
Core Application: app/eventyay/ (selected directories)
| Directory | Purpose |
|---|---|
api/ |
REST API endpoints (Django REST Framework) |
agenda/ |
Agenda and timetable domain logic |
base/ |
Shared models (base/models/), utilities, middleware, and forms (base/forms/) |
cfp/ |
Call-for-proposals and review workflows |
control/ |
Organiser/back-office views, forms, and URLs |
presale/ |
Attendee-facing (ticket purchase) views and forms |
orga/ |
Organiser-facing event management flows and views |
event/ |
Event domain models and related business logic |
common/ |
Cross-cutting helpers shared across modules |
config/ |
Application configuration and settings |
plugins/ |
Plugin infrastructure |
static/ |
Static assets (CSS, JS, images) |
jinja-templates/ |
Jinja HTML templates |
locale/ |
Translation files |
mail/ |
Email rendering and sending |
celery.py / celery_app.py |
Celery task configuration |
This table is intentionally non-exhaustive and focuses on high-traffic modules.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 13d ago First seen · 82 lines · 10 tokens per session scan A c1f06506d0b0
repo-navigation is a skill published in the GitHub repository fossasia/eventyay (1,670 stars, last pushed yesterday), licensed Apache-2.0. It adds 10 tokens to every session and 727 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…