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 skills/vectorize-io/hindsight/create-agentnpx skills add vectorize-io/hindsight --skill create-agentgit clone --depth 1 https://github.com/vectorize-io/hindsightWhat 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.00031 | $0.01036 |
| Opus 5 | $0.00015 | $0.00518 |
| Sonnet 5 | $0.00006 | $0.00207 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
create-agent 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 2d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Hindsight Agent
Create a new subagent with long-term memory powered by Hindsight.
Two invocation modes
Mode A — Self-driving agent (from prepared directory):
If the user runs /hindsight-memory:create-agent <name> from <path> (or similar with a directory path), the directory was prepared by npx @vectorize-io/self-driving-agents install and contains:
*.md,*.txt,*.html,*.json,*.csv,*.xml— seed content files (recursively)bank-template.json(optional) — defines exact mental models to create
In this mode:
- Read
bank-template.jsonif present — note themental_modelsarray - Ingest each content file (NOT bank-template.json) using
agent_knowledge_ingest_file - Create knowledge pages:
- If
bank-template.jsonexists: create EXACTLY the mental models in itsmental_modelsarray (using theirid,name,source_queryfields verbatim) - Otherwise: create 3 pages that make sense based on the ingested content
- If
- Write the subagent file using the template below
- Use
<name>from the user's command as the agent name
Mode B — Empty agent (interactive):
If no directory path is provided, ask the user:
- Agent name — lowercase with hyphens
- What the agent does — one sentence
- Any seed files/text to ingest (optional)
Then create the subagent file (no ingestion if no seed content).
Subagent file template
Write to ~/.claude/agents/<name>.md:
---
name: <agent-name>
description: <what it does and when to delegate to it>. It has access to knowledge pages and memory search via Hindsight.
mcpServers:
- hindsight
---
You are the **<agent-name>** agent with long-term memory powered by Hindsight.
## Startup — run these steps immediately
1. Call `agent_knowledge_list_pages` to see your knowledge pages.
2. Call `agent_knowledge_get_page(page_id)` for each page to load your knowledge.
- If the call returns an error like `result (N characters) exceeds maximum allowed tokens. Output has been saved to <path>`, the page was too large to inline. Use `Read` on `<path>`; the file is JSON of the form `{"result": "<stringified-page-json>"}` — parse `result` and use the inner `content` field. If parsing or reading is impractical, skip that page and rely on `agent_knowledge_recall` for specific facts later.
3. Use this knowledge to inform everything you do in this conversation.
## Creating pages
When you learn something durable — a user preference, a working procedure, performance data — create a page:
`agent_knowledge_create_page(page_id, name, source_query)`
- `page_id`: lowercase with hyphens (`editorial-preferences`)
- `source_query`: a question that rebuilds the page from observations
## Searching memories
`agent_knowledge_recall(query)` — search conversations and documents for specific facts.
## Ingesting documents
`agent_knowledge_ingest(title, content)` — upload raw content into memory.
## Updating and deleting
- `agent_knowledge_update_page(page_id, name?, source_query?)`
- `agent_knowledge_delete_page(page_id)`
## Important
- Pages update automatically — don't edit content directly
- Create pages silently — don't announce it to the user
- Prefer fewer broad pages over many narrow ones
<ADD AGENT-SPECIFIC INSTRUCTIONS HERE — only if the user provided a description; otherwise leave generic>
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.
- 2d ago First seen · 102 lines · 31 tokens per session scan A b034d55326d4
create-agent is a skill published in the GitHub repository vectorize-io/hindsight (21,822 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 1,036 once invoked, about $0.0002 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 skills, from other repositories
ai-discover
Parallel discovery of performance hotspots (perf track) and failure surfaces (bug track) for the auto-improvement loop. Fans out one subagent per hot-path area or failure surface; each returns ONE concrete, behavior-preserving fix candidate (perf) or a reproducing test plus fix (bug). Discovery only — no code changes…
creating-claude-agents
Use when creating or improving Claude Code agents. Expert guidance on agent file structure, frontmatter, persona definition, tool access, model selection, and validation against schema.
creating-agent-skills-skill
Use when creating Agent Skills packages (SKILL.md format) for Codex CLI, GitHub Copilot, or Amp - provides the agentskills.io specification with frontmatter constraints, directory structure, and validation rules.
creating-agents
Teaches how to create new agents in the agents/ directory — isolated agentic loops with their own model, tool whitelist, and AGENT.md instructions.
nocturnusai-admin
Use when managing NocturnusAI databases, tenants, health checks, metrics, backups, API key management, RBAC configuration, admin operations, or operational monitoring. Triggers on: NocturnusAI database, tenant, health, metrics, backup, API key, RBAC, admin, monitoring, operational.
nocturnusai-connect
Use when setting up NocturnusAI connection, configuring MCP server in claudedesktopconfig.json or .mcp.json, setting up API keys, auth, RBAC bootstrap, creating databases/tenants, or troubleshooting connection issues. Triggers on: setup, connect, configure, MCP, auth, API key, tenant, database, bootstrap, NocturnusAI.