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/aerospike/agent-skills/agents-mdgit clone --depth 1 https://github.com/aerospike/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/aerospike/agent-skills/agents-md)<a href="https://agentmods.dev/instructions/aerospike/agent-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/aerospike/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.1 | $0.00933 | $0.00933 |
| Opus 5 | $0.00466 | $0.00466 |
| Sonnet 5 | $0.00187 | $0.00187 |
| Haiku 4.5 | $0.00093 | $0.00093 |
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 6d 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI assistant guidance (tool-agnostic)
Agent Skills live under skills/. This repository ships multiple Aerospike-related skills today; more may appear under skills/ over time. The canonical index is skills/README.md.
| User or task needs… | Start with |
|---|---|
| Local Docker, namespaces/ports/TTL/NSUP, first put/get, Community vs Enterprise images, troubleshooting for a new dev instance | skills/aerospike-getting-started/SKILL.md |
| CDTs, expressions, secondary indexes, batch/scan/query, client policies, performance-oriented client guidance, modeling against a schema that already exists | skills/aerospike-development/SKILL.md |
| Design-time data modeling — deriving a schema from requirements when none exists yet, or redesigning one | skills/aerospike-data-modeling/SKILL.md |
| First program after you already have a running instance | Getting-started examples.md; then development skill if the work goes beyond basic I/O |
| Unsure which skill applies | skills/README.md, then open the matching SKILL.md |
Core database only (not Aerospike Graph). For cluster operations, sizing, or XDR, the development skill defers to Aerospike Operations documentation—see its reference.md.
When to use these instructions
Apply when the user (or task) involves Aerospike, Docker-based Aerospike, client SDK usage (Python, Node.js, Go, Java, C#, etc.), or replacing Redis/Memcached with Aerospike for persistence or scale—then route using the table above.
Read order
Fast path: compiled-skills/aerospike/SKILL.md — published rules for the getting-started, development, and data-modeling skills in one file, updated on every merge to main. Install guide.
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.
- 6d ago First seen · 35 lines · 933 tokens per session scan A ecdc73f669a3
agent-skills AGENTS.md is an instructions file published in the GitHub repository aerospike/agent-skills (18 stars, last pushed 2d ago), licensed Apache-2.0. It adds 933 tokens to every session, about $0.0047 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.
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.
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).