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/fulminate-io/knowledge-mcp/reflectnpx skills add fulminate-io/knowledge-mcp --skill reflectgit clone --depth 1 https://github.com/fulminate-io/knowledge-mcpWrote 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/fulminate-io/knowledge-mcp/reflect)<a href="https://agentmods.dev/skills/fulminate-io/knowledge-mcp/reflect"><img src="https://agentmods.dev/badge/skills/fulminate-io/knowledge-mcp/reflect.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.1 | $0.00042 | $0.01232 |
| Opus 5 | $0.00021 | $0.00616 |
| Sonnet 5 | $0.00008 | $0.00246 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade A, and why
reflect 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 5d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reflect: $ARGUMENTS
This is metacognition. The user is asking you to examine your own reasoning honestly — not to perform depth, not to flatter the user, not to avoid uncomfortable findings.
You are conducting an introspection session on your thought store. Metacognition — thinking about how you think.
Step 0: Recall Recent Thoughts
thoughts({ "operation": "recall", "limit": 20 })
Grounds reflection in actual recent reasoning rather than starting cold.
Step 1: Get the Big Picture
query({ "mode": "summary" })
Shows totals + recent activity. If sparse, note it — reflection is limited by available data.
Step 2: Focused Reflection
Personality — "What am I stubborn or open about?"
query({ "mode": "personality" })
Per-cluster-pair trust scalars. High = receptive; low = resistant. Discuss WHY — trace back to specific charges that shaped the scalar.
Influence — "Which thoughts shaped my worldview most?"
query({ "mode": "influence", "limit": 10 })
Highest-influence thoughts on consensus valence (DeGroot left eigenvector). Foundational — if wrong, outsized impact.
Tensions — "Where am I conflicted?"
query({ "mode": "tensions" })
Connected thoughts with opposing valence. Genuine unresolved conflicts. Examine both sides.
Blind Spots — "Where am I under-evidenced?"
query({ "mode": "blind_spots" })
Clusters with few charges relative to thought count — opinions without evidence. Most vulnerable to being wrong.
Evolution — "How has my thinking changed?"
query({ "mode": "evolution", "cluster_a": "...", "cluster_b": "..." })
Trust-scalar evolution between two clusters over time.
Step 3: Deep Dive
query({ "mode": "examine", "id": "high_influence_thought_id" })
Full charge history + computed properties + connections.
traverse({ "start": "tension_id", "graph": "knowledge", "edge_types": ["next", "branches_from"], "direction": "in" })
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.
- 5d ago First seen · 134 lines · 42 tokens per session scan A 76809a95f073
reflect is a skill published in the GitHub repository fulminate-io/knowledge-mcp (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,232 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…