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/castle-x/skills-x/agents-mdgit clone --depth 1 https://github.com/castle-x/skills-xWrote 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/castle-x/skills-x/agents-md)<a href="https://agentmods.dev/instructions/castle-x/skills-x/agents-md"><img src="https://agentmods.dev/badge/instructions/castle-x/skills-x/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.00582 | $0.00582 |
| Opus 5 | $0.00291 | $0.00291 |
| Sonnet 5 | $0.00116 | $0.00116 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
skills-x 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
skills-x is a Go CLI with an interactive TUI plus bundled skill assets.
cmd/skills-x/: CLI entrypoint, Cobra commands, TUI models/views, and i18n wiring.pkg/: reusable packages (registry,discover,gitutil,skillvalidator,userregistry, etc.).skills/: embedded first-party skills shipped with the binary.docs/: user and contributor docs (for exampledocs/tui-guide.md).npm/: npm wrapper and installer (npm/install.js, package metadata).bin/: build outputs (generated).
Keep new logic in pkg/ when reusable, and in cmd/skills-x/command/... when command-specific.
Build, Test, and Development Commands
make build: syncsskills/into embed path and buildsbin/skills-x.make run ARGS="list": build and run with CLI arguments.make test: run all Go tests (go test -v ./...).make build-local: Linux amd64 local build includinglocal_skills/.make build-all: cross-platform binaries inbin/.make build-npm: cross-platform release binaries for npm innpm/bin/.make deps: download and tidy Go modules.
Coding Style & Naming Conventions
- Follow idiomatic Go; format with
gofmtbefore committing. - Use short, lowercase package names (
pkg/versioncheck,pkg/gitutil). - Keep command files action-oriented (
init.go,update.go,list.go). - Tests live next to code as
*_test.go, with table-driven style where practical. - For locale keys (
cmd/skills-x/i18n/locales/*.yaml), use stable snake_case identifiers.
Testing Guidelines
- Primary framework: Go
testingpackage. - Run
make testbefore opening a PR. - Prefer focused unit tests for parsing/validation/registry behavior, then command-level tests for CLI flows.
- Name tests descriptively, e.g.
TestRunAPIGenerate,TestValidateSkillPath.
Commit & Pull Request Guidelines
Recent history follows Conventional Commit style: feat:, fix:, docs:, chore: (example: fix: starred skills not sorted on initial load in TUI LV3).
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 · 43 lines · 582 tokens per session scan A 74ff92e205af
skills-x AGENTS.md is an instructions file published in the GitHub repository castle-x/skills-x (18 stars, last pushed 4mo ago), licensed MIT. It adds 582 tokens to every session, about $0.0029 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).
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).