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 commands/donbr/graphiti-fastmcp/verifygit clone --depth 1 https://github.com/donbr/graphiti-fastmcpWrote 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/commands/donbr/graphiti-fastmcp/verify)<a href="https://agentmods.dev/commands/donbr/graphiti-fastmcp/verify"><img src="https://agentmods.dev/badge/commands/donbr/graphiti-fastmcp/verify.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.00000 | $0.00308 |
| Opus 5 | $0.00000 | $0.00154 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
verify 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 3d 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.
What it actually says
Run the Day 1 verification sequence to confirm the environment is working.
Instructions
Execute these three checks in order. Report results but do NOT attempt fixes without user approval.
Check 1: Server Health
mcp__graphiti-local__get_status()
Expected: Status OK with database connection confirmed.
Check 2: Query Available Groups
mcp__docker__read_neo4j_cypher(
query="MATCH (e:Episodic) RETURN DISTINCT e.group_id AS group_id, count(*) AS episodes ORDER BY episodes DESC"
)
Expected: List of group_ids with episode counts. Primary groups are graphiti_meta_knowledge and graphiti_reference_docs.
Check 3: Test Semantic Search
mcp__graphiti-local__search_nodes(
query="graphiti best practices",
group_ids=["graphiti_meta_knowledge"],
max_nodes=5
)
Expected: Returns relevant entity nodes.
After Running
Report your findings to the user:
- ✅ All checks passed - environment is healthy
- ⚠️ Some checks failed - describe what you found, ASK before fixing
- ❌ Connection errors - report error, do NOT attempt destructive fixes
Remember
- Empty results usually mean wrong
group_idsparameter, NOT a broken system - NEVER run
clear_graphor delete commands without explicit user request - When in doubt, ASK THE USER
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.
- 3d ago First seen · 43 lines · 0 tokens per session scan A bf4952f1cbc1
verify is a command published in the GitHub repository donbr/graphiti-fastmcp (0 stars, last pushed 8mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 308 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.