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 rjmurillo/ai-agents --skill exploring-knowledge-graphgit clone --depth 1 https://github.com/rjmurillo/ai-agentsWrote 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/rjmurillo/ai-agents/exploring-knowledge-graph)<a href="https://agentmods.dev/skills/rjmurillo/ai-agents/exploring-knowledge-graph"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/exploring-knowledge-graph.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.01248 |
| Opus 5 | $0.00023 | $0.00624 |
| Sonnet 5 | $0.00009 | $0.00250 |
| Haiku 4.5 | $0.00005 | $0.00125 |
Grade A, and why
exploring-knowledge-graph 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 4d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exploring the Knowledge Graph
Forgetful stores knowledge as an interconnected graph: memories link to other memories, entities link to memories, and entities relate to each other. Deep exploration reveals context that simple queries miss.
Triggers
| Trigger Phrase | Operation |
|---|---|
what do you know about X |
Full knowledge graph traversal |
how do I explore the knowledge graph |
Graph exploration workflow |
how are these concepts connected |
Entity relationship traversal |
give me comprehensive context on X |
Deep multi-phase exploration |
map out related knowledge for X |
Entity discovery and memory linking |
When to Explore
Explore the knowledge graph when:
- Starting complex work that spans multiple topics
- User asks "what do you know about X"
- Planning requires understanding existing decisions/patterns
- Investigating how concepts connect across projects
- Need comprehensive context, not just top search results
Exploration Phases
Track visited IDs to prevent cycles. Execute phases sequentially.
Phase 1: Semantic Entry Point
execute_forgetful_tool("query_memory", {
"query": "<topic>",
"query_context": "Exploring knowledge graph for comprehensive context",
"k": 5,
"include_links": true,
"max_links_per_primary": 5
})
Collect: primary_memories + linked_memories (1-hop connections).
Phase 2: Expand Memory Details
For key memories, get full details:
execute_forgetful_tool("get_memory", {"memory_id": <id>})
Extract: document_ids, code_artifact_ids, project_ids, additional linked_memory_ids.
Phase 3: Entity Discovery
Find entities in discovered projects:
execute_forgetful_tool("list_entities", {
"project_ids": [<discovered project ids>]
})
Phase 4: Entity Relationships
For relevant entities, map relationship graph:
execute_forgetful_tool("get_entity_relationships", {
"entity_id": <id>,
"direction": "both"
})
What ships with it
1 file 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.
- 4d ago First seen · 178 lines · 47 tokens per session scan A 6180becfe29b
exploring-knowledge-graph is a skill published in the GitHub repository rjmurillo/ai-agents (45 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 1,248 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-09-03.
Other skills, from other repositories
context-recovery
Recover missing conversation context after explicit compaction or truncation, or when the user explicitly asks to recover prior work. Use for requests such as "where were we before compaction?" when the current thread is insufficient. Do not trigger on a generic "continue" when the current thread already provides an…
ci-cd
A guide for designing automated build and delivery workflows with GitHub Actions. These workflows can run checks such as tests, code-quality scans, coverage checks, and builds when code is pushed or a pull request is opened.
context-search
A continuity workflow for finding context from earlier coding-agent sessions. It can inspect continuation notes and session records when a task refers to previous work.
abmind-runtime-operations
Inspect and maintain abmind memory, persona files, sleep, backups, encryption, and runtime health.
memory-search
Search persistent memory for facts, decisions, and past conversations.
topic-save
Save and manage topic-specific knowledge files from conversations.