Borrowing it
Nothing to install: this file belongs to shennawardana23/skillme. 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/shennawardana23/skillme/main/AGENTS.mdgit clone --depth 1 https://github.com/shennawardana23/skillmeWrote 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/shennawardana23/skillme/agents-md)<a href="https://agentmods.dev/instructions/shennawardana23/skillme/agents-md"><img src="https://agentmods.dev/badge/instructions/shennawardana23/skillme/agents-md/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/instructions/shennawardana23/skillme/agents-md"><img src="https://agentmods.dev/badge/instructions/shennawardana23/skillme/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00499 | $0.00499 |
| Opus 5.5 | $0.00200 | $0.00200 |
| Sonnet 5.5 | $0.00100 | $0.00100 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
skillme 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 7d 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
open-slide — Agent Guide
You are authoring slides in this repo. Every slide is arbitrary React code that you write.
Hard rules
- Put your slide under
slides/<kebab-case-id>/. - The entry is
slides/<id>/index.tsx. - Put slide-specific images/videos/fonts under
slides/<id>/assets/. For assets reused across decks or themes (logos, avatars), use the globalassets/folder and import via@assets/.... - Do not touch
package.json,open-slide.config.ts, or other slides. - Do not add dependencies. Use only
reactand standard web APIs.
Which skill to use
- Drafting a new deck — use the
create-slideskill. It walks through scoping questions, structure, and hand-off. - Applying inspector comments (
@slide-commentmarkers in a page) — use theapply-commentsskill. - Creating or extracting a theme — use the
create-themeskill. Themes live as markdown underthemes/<id>.mdand are read bycreate-slidebefore authoring. - Resolving "this page" / "this element" — when the user references the current slide or selection without naming it, consult the
current-slideskill. It reads the dev server'snode_modules/.open-slide/current.jsonto find which slide, page, and inspector-picked element they mean. - Any other slide edit — read the
slide-authoringskill before writing. It is the technical reference for everything insideslides/<id>/: file contract, the 1920×1080 canvas, type scale, palette, layout, assets, self-review checklist, and anti-patterns.create-slideandapply-commentsboth defer to it for the how.
Keep this file short: hard rules only. All deeper guidance lives in the skills above.
Updating skills
The skills above are managed by @open-slide/core. Do not edit them in place. To pull the latest versions:
pnpm up @open-slide/core
pnpm sync:skills
pnpm dev will also detect drift on startup and offer to sync. pnpm sync:skills --dry-run (via pnpm exec open-slide sync:skills --dry-run) previews changes without writing.
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.
- 7d ago First seen · 33 lines · 499 tokens per session scan A f94fd39715ff
skillme AGENTS.md is an instructions file published in the GitHub repository shennawardana23/skillme (3 stars, last pushed 8d ago), licensed Apache-2.0. It adds 499 tokens to every session, about $0.0020 per session on Opus 5.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-10-16.
Other instructions, from other repositories
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.