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/stevepridemore/graph-memory/graph-asknpx skills add stevepridemore/graph-memory --skill graph-askgit clone --depth 1 https://github.com/stevepridemore/graph-memoryWhat 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.00043 | $0.01829 |
| Opus 5 | $0.00022 | $0.00915 |
| Sonnet 5 | $0.00009 | $0.00366 |
| Haiku 4.5 | $0.00004 | $0.00183 |
Grade A, and why
graph-ask 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The user wants to ask a natural language question about the memory graph. You will generate the Cypher query yourself and execute it via the graph_cypher MCP tool.
Arguments: $ARGUMENTS
GRAPH SCHEMA
All entity nodes carry both :Entity and their type label (e.g., :Entity:Person). All entities have: id (STRING), name (STRING), subtype (STRING), confidence (FLOAT), times_mentioned (INTEGER), first_seen (DATETIME), last_seen (DATETIME), source_file (STRING).
Node labels (8 types):
- Person: role, relationship_to_user, organization, email
- Project: status, stack, description, directory, start_date
- Preference: domain, key, value, times_confirmed
- Concept: category, user_expertise, description
- Decision: what, why, context, reversible (BOOLEAN), status, decided_date
- Fact: domain, content, source, verified (BOOLEAN)
- Event: description, event_date (DATETIME), duration, outcome, location, status
- Object: object_type, description, status, url, version
Relationship types (17 total, all have weight FLOAT and last_confirmed DATETIME):
- WORKS_ON (Person->Project): role, since
- PREFERS (Person->Preference): strength
- KNOWS_ABOUT (Person->Concept): depth
- DEPENDS_ON (Project->Project): dependency_type
- USES_TECH (Project->Concept): role
- DECIDED_FOR (Decision->any)
- SUPERSEDES (Decision->Decision): reason, superseded_date
- CONTRADICTS (any->any): description, detected_date, resolved (BOOLEAN), resolution
- RELATED_TO (any->any): relationship_type (similar_to, part_of, enables, impacts, depends_on, alternative_to, derived_from, implements, extends, configured_by)
- ALIAS_OF (any->any)
- PARTICIPATED_IN (Person->Event): role
- OCCURRED_DURING (Event->Project)
- PRODUCED (Event->Decision|Object|Fact)
- TRIGGERED_BY (Event->Event)
- USES (Project|Person->Object): purpose
- HOSTED_ON (Object->Object)
- PRODUCED_BY (Object->Project|Event)
QUERY TEMPLATES
Use these tested templates for common question patterns. Fill in the $param values and adjust as needed.
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 · 177 lines · 43 tokens per session scan A b721b499a677
graph-ask is a skill published in the GitHub repository stevepridemore/graph-memory (2 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 1,829 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-31.
Other skills, from other repositories
ori-memory
Persistent agent memory with learning retrieval. Knowledge graph on markdown files — capture insights, decisions, research, and learnings during work, then retrieve them weeks or months later. Use when knowledge is too valuable to lose but too much to inject into every prompt.
svoboda-profiler
Use when asked to profile someone, unpack a person, build a psychological portrait, run a Svoboda session, or map life state. Triggers on распаковка, профилирование, психопортрет, точка А, колесо баланса, profile someone, unpack, svoboda session.
vault-scaffolder
Use when a completed svoboda profile.yaml exists and a new Personal OS needs to be personalized in the current workspace.
install-waggle
Install the official Waggle plugin locally for Codex from the latest stable Abhigyan-Shekhar/Waggle-mcp GitHub Release. Use for explicit requests such as "Install Waggle", "Set up Waggle", "Install Waggle for Codex", or "Enable Waggle". Do not use for Waggle operation, repair, updates, configuration, or memory…
lint
Use weekly or after major ingest sessions to check wiki health.
start
One-word self-unfolding onboarding. Sets up a fresh, unpersonalized vault end-to-end — installs the memory engine, runs the profile interview, scaffolds the vault, and teaches the user as it goes. The single front door.