Borrowing it
Nothing to install: this file belongs to badsectorlabs/ludus-skills. 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/badsectorlabs/ludus-skills/main/AGENTS.mdgit clone --depth 1 https://github.com/badsectorlabs/ludus-skillsWrote 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/instructions/badsectorlabs/ludus-skills/agents-md)<a href="https://agentmods.dev/instructions/badsectorlabs/ludus-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/badsectorlabs/ludus-skills/agents-md.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.1 | $0.00463 | $0.00463 |
| Opus 5 | $0.00231 | $0.00231 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
ludus-skills AGENTS.md 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ludus-skills CLAUDE.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This repository is a skills collection, not an application runtime. Keep changes scoped to skills/.
skills/<skill-name>/SKILL.md: core agent instructions for one skill.skills/<skill-name>/references/*.md: detailed source-backed reference material.skills/<skill-name>/agents/openai.yaml: UI metadata (display_name,short_description,default_prompt).- Root docs:
README.mdand this guide.
Current skills are environment-guide, ludus-cli, range-config, and troubleshooting.
Build, Test, and Development Commands
There is no compile/build step in this repo. Validate by installing skills locally:
npx skills add .
npx skills list
Use the published install path when testing consumer behavior:
npx skills add badsectorlabs/ludus-skills
Coding Style & Naming Conventions
- Use Markdown with concise, actionable instructions.
- Skill folders must be kebab-case (example:
range-config). - Keep
SKILL.mdfrontmatter minimal:nameanddescription. - Put detailed docs in
references/; keepSKILL.mdfocused on workflow and decision guidance. - For long reference files, include a
## Table of Contents.
Testing Guidelines
- Prefer factual updates sourced from official Ludus documentation.
- After edits, run local install checks (
npx skills add ...) and confirm skills are discoverable. - Validate that links/paths in
SKILL.mdresolve correctly (for example,references/schema.md). - If behavior changed, test one realistic prompt per modified skill.
Commit & Pull Request Guidelines
- Follow conventional-style commit prefixes with emoji, as used in repo history:
feat: ✨ ...docs: 📚 ...
- Keep subject lines imperative and concise.
- Commit only files related to your change.
- Include DCO sign-off on commits (
git commit -s). - PR/MR descriptions should state:
- what changed,
- why it changed,
- which skills/files were updated,
- how you validated locally.
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.
- 8d ago First seen · 52 lines · 463 tokens per session scan A 4b533c946818
ludus-skills AGENTS.md is an instructions file published in the GitHub repository badsectorlabs/ludus-skills (9 stars, last pushed 28d ago), licensed MIT. It adds 463 tokens to every session, about $0.0023 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.