grounded-knowledge-workflow

grounded-knowledge-workflow is a skill for Codex from dimosgit/grounded-knowledge-engine. It costs 91 tokens per session (2,227 once invoked), scanned A, original, MIT.

A workflow for answering questions from documents and other local project evidence. It can also resume a named project and keep explicit project knowledge.

In plain words
What is it for?
Use it to answer questions about your files, client context, previous research, or project state, with citations when appropriate.
Why use it?
It helps avoid mixing information from unrelated workspaces or relying on unsupported memory.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions Codex.

Good fit Use it to answer questions about your files, client context, previous research, or project state, with citations when appropriate.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dimosgit/grounded-knowledge-engine/grounded-knowledge-workflow
Install

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.

Any agent
npx skills add dimosgit/grounded-knowledge-engine --skill grounded-knowledge-workflow
Clone the repo
git clone --depth 1 https://github.com/dimosgit/grounded-knowledge-engine

Made for: Codex.

Wrote 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.

agentmods badge for grounded-knowledge-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/dimosgit/grounded-knowledge-engine/grounded-knowledge-workflow/github.svg)](https://agentmods.dev/skills/dimosgit/grounded-knowledge-engine/grounded-knowledge-workflow)
Your own site
<a href="https://agentmods.dev/skills/dimosgit/grounded-knowledge-engine/grounded-knowledge-workflow"><img src="https://agentmods.dev/badge/skills/dimosgit/grounded-knowledge-engine/grounded-knowledge-workflow/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.

agentmods 80×15 button for grounded-knowledge-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/dimosgit/grounded-knowledge-engine/grounded-knowledge-workflow"><img src="https://agentmods.dev/badge/skills/dimosgit/grounded-knowledge-engine/grounded-knowledge-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 91 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,227 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00091 $0.02227
Opus 5.5 $0.00036 $0.00891
Sonnet 5.5 $0.00018 $0.00445
Haiku 4.5 $0.00009 $0.00223

Measured 9d ago against content hash fe71c552e445, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

grounded-knowledge-workflow 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 9d 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.

skills/grounded-knowledge-workflow/SKILL.md · 205 lines

How it starts

The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Grounded Knowledge Workflow

Use the engine as shared memory, not as a replacement for judgment. Keep this skill thin: select the semantic operation and let the MCP server and CLI enforce retrieval, project scope, citations, and writes.

Use the one-call Q&A fast path

  • For an ordinary definition, recall, explanation, or comparison, call kb.answer_and_capture exactly once with responseMode: auto and responseFormat: compact, and captureStrategy: auto.
  • Do not call kb.search or kb.get_record before it. The answer tool performs its own retrieval and grounding. Without a noteBody finding it never writes.
  • Return the answer, citations, capture status, tokenUsage, and timings. When the KB lacked the answer and the result is durable, first apply "Retain automatically, update first" below. Do no other maintenance unless asked.

Coordinate complex implementation separately

In a source checkout, only substantial implementation work with independent workstreams or a named high-risk decision can use the optional skills/complex-task-workflow/SKILL.md for token-first routing and bounded native workers. Do not load it for routine or sequential work. Check that the file exists: the published package does not include this optional skill. If it is absent, continue using the active client's normal implementation workflow without installing anything or treating the missing skill as a blocker.

This skill continues to own local grounding, explicit project resume, and authorized durable capture.

Choose the operation

  1. For a named project or “continue where I stopped,” call kb.resume_project with the explicit projectId.
  2. For an evidence-only search request, call kb.search.
  3. For one known record, call kb.get_record by path, title, slug, or filename.
  4. For a grounded answer that may retain useful context, call kb.answer_and_capture.
  5. For project creation and administration, use the deterministic gke project CLI rather than inventing an MCP file-management workflow.
  6. When the user explicitly asks to preserve a project handoff or progress boundary, use gke checkpoint; never create one merely because a project was viewed or resumed.
  7. When the user explicitly asks to preserve or inspect a durable decision, use the full-profile decision MCP tools when available. Use the local gke decisions CLI for administration or when the MCP server is running the core profile. Local Cockpit preview/apply may append a reviewed change; the public Cockpit remains read-only.

Read the full file on GitHub · 205 lines

Files

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.

Changes

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.

  1. 9d ago Changed · +13 lines fe71c552e445
  2. 24d ago Changed · +16 lines 04dc7759cb84
  3. 1mo ago First seen · 176 lines · 91 tokens per session scan A 386f3e72424d

Subscribe to this mod's changes

grounded-knowledge-workflow is a skill published in the GitHub repository dimosgit/grounded-knowledge-engine (5 stars, last pushed 10d ago), licensed MIT. It adds 91 tokens to every session and 2,227 once invoked, about $0.0004 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-31.

Related

Other skills, from other repositories

my-wiki

A skill for managing a local Markdown knowledge vault that stores captured webpages, PDFs, Office files, notes, images, folders, and ZIP files. It links preserved source material, called References, to durable topic pages, called Concepts.

NimaChu/my-wiki · 51 tokens

obsidian-vault-workflow

Use this skill when a user asks an agent to inspect, organize, summarize, or update an Obsidian vault through this MCP server.

aka-kika/kika-obsidian-mcp · 0 tokens

vault-for-llm

Connect OpenClaw to Vault Agent Memory as a local-first governed project memory layer. Search first, then bounded-read cited source ranges; propose new memories as candidates instead of writing directly into active memory.

zycaskevin/Vault-Agent-Memory · 46 tokens

context

Use whenever the user asks about their own work, projects, decisions, people, preferences or past sessions, and before ending any session that produced something worth keeping. The user's Context is their own notes, reached through the context MCP server; this skill says when to read it and how to write back.

Supa-Media/context · 64 tokens

how-we-define-chaos

How Context scores a workspace's chaos, and how to organize notes so it goes down. Use when the user asks you to tidy, organize, clean up or restructure their notes or folders, asks about their chaos score, or when a write or move answer reports the score got messier.

Supa-Media/context · 65 tokens

any-mcp

Use when an agent needs to read, search, create, edit, organize, upload, or chat with Anytype through the bounded any-mcp server. Covers safe tool selection, exact identifier chaining, optional toolsets, common PKM workflows, and the narrow anyr fallbacks for chat subscriptions and rich chat blocks.

stevelr/anytype · 68 tokens