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/documentationnpx skills add fossasia/eventyay --skill documentationgit 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/documentation)<a href="https://agentmods.dev/skills/fossasia/eventyay/documentation"><img src="https://agentmods.dev/badge/skills/fossasia/eventyay/documentation.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.00007 | $0.00290 |
| Opus 5 | $0.00003 | $0.00145 |
| Sonnet 5 | $0.00001 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
documentation 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.
What it actually says
Skill: Documentation
Documentation Files
| File | Purpose |
|---|---|
README.rst |
Project overview and getting-started guide (reStructuredText) |
CONTRIBUTING.md |
Contributor guidelines and development setup |
DEPLOYMENT.md |
Production deployment walkthrough |
.github/instructions/dockerfile.instructions.md |
Docker Compose usage and container reference |
doc/ |
Extended project documentation |
How to Update README.rst
- Written in reStructuredText (
.rst). - Keep the getting-started steps current when CLI commands or workflows change.
- Maintain existing section structure; add new sections at a logical location.
How to Update doc/
- Files may be
.rstor.mddepending on the sub-section. - Follow the existing style of the surrounding files.
- Run a documentation build locally if a build pipeline is configured.
How to Update CONTRIBUTING.md
- Keep the setup instructions in sync with
README.rst. - Document any new tooling or workflow changes that affect contributors.
General Guidelines
- Keep documentation concise and accurate.
- Prefer concrete examples over abstract descriptions.
- When changing a CLI command, update all documentation that references it.
- Documentation changes do not require tests unless there are specific doc-tests.
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.
- 4d ago First seen · 41 lines · 7 tokens per session scan A f9647dc18c85
documentation is a skill published in the GitHub repository fossasia/eventyay (1,655 stars, last pushed today), licensed Apache-2.0. It adds 7 tokens to every session and 290 once invoked, about $0.0000 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…