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 instructions/get-convex/agent-skills/agents-mdgit clone --depth 1 https://github.com/get-convex/agent-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/get-convex/agent-skills/agents-md)<a href="https://agentmods.dev/instructions/get-convex/agent-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/get-convex/agent-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 | $0.00556 | $0.00556 |
| Opus 5 | $0.00278 | $0.00278 |
| Sonnet 5 | $0.00111 | $0.00111 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
agent-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 5d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
Rules for contributing to this repository.
Skill Philosophy
Skills in this repository should be narrowly focused on a specific task or workflow.
A good skill helps an agent take a concrete action, for example:
- set up authentication
- design a schema
- create a Convex function
- plan a migration
Do not create skills that mainly provide generic background information or broad documentation. If content is mostly reference material, it should usually live in docs, not as a standalone skill.
Reference material is fine inside a skill when it directly helps complete the task the skill is for.
Before contributing, review the core Agent Skills docs:
- Overview
- What are skills?
- Specification
- Optimizing skill descriptions
- Evaluating skill output quality
If the skill uses bundled scripts, also review Using scripts in skills.
Style Guidelines
- No emojis in any markdown files or code comments
- Use
Yes/Noin tables instead of checkmarks or emoji - Keep examples concise and focused
- Use
// Bad:and// Good:comments in code examples - Follow existing file patterns in
skills/
File Structure
Each skill should have:
- Clear heading with brief description
- "When to Use" section
- Code examples showing bad vs good patterns
- Complete, runnable examples
- Checklist at the end
Maintenance
- If skills are added, removed, renamed, or substantially repositioned, update
the root
README.md - Keep the skill list in the root
README.mdin sync with the current contents ofskills/
Validation
- Do not assume a skill is good just because it reads well
- Validate skills by trying to use them in a realistic temp project or sandbox
- Push the task as far as possible without human help
- If human intervention is required, stop and ask explicitly for the exact step needed
- After the run, feed what you learned back into the skill with clearer instructions, steps, gotchas, or validation checks
- For UI-facing skills, validate the browser flow as part of skill authoring, not just the code or CLI steps
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.
- 5d ago First seen · 79 lines · 556 tokens per session scan A 267fb353f08f
agent-skills AGENTS.md is an instructions file published in the GitHub repository get-convex/agent-skills (51 stars, last pushed 4d ago), licensed Apache-2.0. It adds 556 tokens to every session, about $0.0028 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 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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.