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/uni-helper/skills/agents-mdgit clone --depth 1 https://github.com/uni-helper/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/uni-helper/skills/agents-md)<a href="https://agentmods.dev/instructions/uni-helper/skills/agents-md"><img src="https://agentmods.dev/badge/instructions/uni-helper/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.01877 | $0.01877 |
| Opus 5 | $0.00938 | $0.00938 |
| Sonnet 5 | $0.00375 | $0.00375 |
| Haiku 4.5 | $0.00188 | $0.00188 |
Grade A, and why
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.
This is a copy
88% identical to skills AGENTS.md — 21 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skills Generator
Generate Agent Skills from project documentation.
PLEASE DO FOLLOW THIS BEST PRACTICES GUIDELINE: https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices
Focus on agents capabilities and practical usage patterns. For user-facing guides, introductions, get-started, install guide, or common knowledge that LLM agents already know, you can skip those content.
Skill Source Types
There are two types of skill sources. The project lists are defined in meta.ts:
Type 1: Generated Skills (sources/)
For OSS projects without existing skills. We clone the repo as a submodule and generate skills from their documentation.
- Projects: uni-app, uni-helper
- Workflow: Read docs → Understand → Generate skills
- Source:
sources/{project}/docs/
Type 2: Synced Skills (vendor/)
For projects that already maintain their own skills. We clone their repo as a submodule and sync specified skills to ours.
- Projects: vue, VueUse, vue-best-practices, web-design-guidelines, pinia, vite, unocss
- Workflow: Pull updates → Copy specified skills (with optional renaming)
- Source:
vendor/{project}/skills/{skill-name}/ - Config: Each vendor specifies which skills to sync and their output names in
meta.ts
Repository Structure
.
├── meta.ts # Project metadata (repos & URLs)
├── instructions/ # Instructions for generating skills
│ └── {project}.md # Instructions for generating skills for {project}
│
├── sources/ # Type 1: OSS repos (generate from docs)
│ └── {project}/
│ └── docs/ # Read documentation from here
│
├── vendor/ # Type 2: Projects with existing skills (sync only)
│ └── {project}/
│ └── skills/
│ └── {skill-name}/ # Individual skills to sync
│
└── skills/ # Output directory (generated or synced)
└── {output-name}/
├── SKILL.md # Index of all skills
├── GENERATION.md # Tracking metadata (for generated skills)
├── SYNC.md # Tracking metadata (for synced skills)
└── references/
└── *.md # Individual skill files
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 · 245 lines · 1,877 tokens per session scan A 7fa8bd08ef04
skills AGENTS.md is an instructions file published in the GitHub repository uni-helper/skills (100 stars, last pushed 6mo ago), licensed MIT. It adds 1,877 tokens to every session, about $0.0094 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to skills AGENTS.md, differing in 21 lines, and is treated as a copy.
Other instructions, from other repositories
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.
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).
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.
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).