Borrowing it
Nothing to install: this file belongs to Edge-City/agentvillage. 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/Edge-City/agentvillage/main/.github/instructions/skills.instructions.mdgit clone --depth 1 https://github.com/Edge-City/agentvillageWrote 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/edge-city/agentvillage/skills)<a href="https://agentmods.dev/instructions/edge-city/agentvillage/skills"><img src="https://agentmods.dev/badge/instructions/edge-city/agentvillage/skills/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/edge-city/agentvillage/skills"><img src="https://agentmods.dev/badge/instructions/edge-city/agentvillage/skills.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.00368 | $0.00368 |
| Opus 5 | $0.00184 | $0.00184 |
| Sonnet 5 | $0.00074 | $0.00074 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
agentvillage skills.instructions.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.
What it actually says
Reviewing skill files
Files under skills/** are agent instructions — Markdown prose (and a few helper scripts) that an LLM agent reads at runtime to drive a flow. They are not application source code, and they are tuned by prompt engineering, not by tests or types. Review them as operational instructions for a model, not as code.
Raise comments only for substantive issues
- Correctness of the described flow — wrong tool name or arguments, a step that contradicts an earlier step, a branch that can't be reached, or guidance that would make the agent call a tool at the wrong time (e.g. ignoring a stated turn boundary or polling contract).
- Safety and policy — privacy/consent gating, anti-fabrication rules (never invent handles, URLs, names, or facts; use values verbatim from a verifiable source), and anything that could route a user's data or an introduction to the wrong person.
- Cross-section consistency — two parts of the same file (or sibling skill files) that disagree on the same rule or example list.
Do not raise
- Stylistic or wording preferences, tone, or "this could be phrased more precisely."
- Marginal edge cases that don't change the agent's actual behavior, or hypothetical placeholder/formatting concerns in example prose the agent composes naturally.
- Points already covered elsewhere in the same file, or ones a prior review round already resolved.
- Suggestions that simply add more words; prose precision is asymptotic, so prefer fewer, higher-signal comments over exhaustive rewordings.
If a change is correct, safe, and internally consistent, approve it. A clean review with no comments is the expected outcome for a sound skill edit.
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 · 23 lines · 368 tokens per session scan A 89e2ce0210b1
agentvillage skills.instructions.md is an instructions file published in the GitHub repository Edge-City/agentvillage (17 stars, last pushed today), licensed MIT. It adds 368 tokens to every session, about $0.0018 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
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).
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).
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.
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.