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 skills add aerospike/agent-skills --skill aerospike-getting-startedgit 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/skills/aerospike/agent-skills/aerospike-getting-started)<a href="https://agentmods.dev/skills/aerospike/agent-skills/aerospike-getting-started"><img src="https://agentmods.dev/badge/skills/aerospike/agent-skills/aerospike-getting-started/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/skills/aerospike/agent-skills/aerospike-getting-started"><img src="https://agentmods.dev/badge/skills/aerospike/agent-skills/aerospike-getting-started.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Output Handling · line 197 Model output is used without validation or sanitization. Unvalidated output injected into downstream contexts (SQL, shell, HTML) enables injection attacks and arbitrary code execution.Fix: Validate and sanitize all model output before using it in downstream contexts. Use parameterized queries for SQL, shell quoting for commands, and HTML encoding for web output.
- medium Excessive Agency · line 101 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium MCP Rug Pull · line 150 Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.Fix: Pin the image: image:tag or image@sha256:abc123
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.00137 | $0.03578 |
| Opus 5.5 | $0.00055 | $0.01431 |
| Sonnet 5.5 | $0.00027 | $0.00716 |
| Haiku 4.5 | $0.00014 | $0.00358 |
Grade A, and why
aerospike-getting-started 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 1mo 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Aerospike Database: getting started
When to use
Use this skill when the user asks to:
- Set up Aerospike, a real-time database, or a low-latency NoSQL store.
- Replace Redis or Memcached with a persistent, clustered alternative.
- Add a high-throughput key-value or document database to their project. (Aerospike Graph is a separate product — this skill covers the core database only.)
- Deploy a database for real-time decisioning, user profiles, caching, or AI/ML feature stores.
Mental model
- Hierarchy: A namespace holds sets; each record is addressed by a key (namespace + set + user key). Bins are name/value fields on the record. Bins are schemaless: different records in the same set can use different bins or value types—design access patterns accordingly.
- Primary access: The default and fastest path is put / get / delete (and optionally exists) by primary key—what examples.md demonstrates. This is not SQL with arbitrary joins or a fixed table schema.
- Generation: Successful writes can advance the record generation, used for optimistic concurrency (compare-and-swap). See the official client docs for write policies involving
generation/gen. - Vocabulary: Use namespace, set, record, and bin consistently (see Critical rules below). Avoid treating Aerospike like a relational database.
First operations map
Use this map so new users know what to reach for after the first put/get:
| Stage | What to use | Where to start |
|---|---|---|
| First program | Single-record put, get, delete | examples.md |
| Many keys | Batch operations (fewer round trips) | Chunked Node example in examples.md; every client has batch APIs—see Client libraries for your language |
| Lookup by bin value (not primary key) | Secondary index + query | Not part of the minimal Docker + first read/write path; see Secondary index queries |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +1 lines ab9d8ce983d5
- 2mo ago First seen · 223 lines · 137 tokens per session scan A 8890ae490602
aerospike-getting-started is a skill published in the GitHub repository aerospike/agent-skills (19 stars, last pushed 16d ago), licensed Apache-2.0. It adds 137 tokens to every session and 3,578 once invoked, about $0.0005 per session on Opus 5.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.
aerospike-getting-started compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| aerospike-getting-startedaerospike/agent-skills | Skill | 19 | 16d ago | Apache-2.0 | A | 137 | Claude Code, Codex |
| create-prprisma/orm | Skill | 48k | yesterday | Apache-2.0 | A | 48 | Claude Code, Codex |
| schema-explorationlangchain-ai/deepagents | Skill | 31k | yesterday | MIT | A | 57 | Claude Code, Codex |
| atlas-mssqlariga/atlas | Skill | 8.8k | yesterday | Apache-2.0 | A | 163 | Claude Code |
| ha-data-storesshiwenwen/hope-agent | Skill | 1.9k | yesterday | MIT | A | 115 | Claude Code, Codex |
| nornicdb-cypher-queriesorneryd/NornicDB | Skill | 923 | yesterday | MIT | A | 79 | Claude Code, Codex |
| volcengine-rds-postgresqlbytedance/agentkit-samples | Skill | 484 | today | Apache-2.0 | A | 63 | Claude Code, Codex |