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.
git clone --depth 1 https://github.com/julymetodiev/post-cortexWrote 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/agents/julymetodiev/post-cortex/knowledge-analyst)<a href="https://agentmods.dev/agents/julymetodiev/post-cortex/knowledge-analyst"><img src="https://agentmods.dev/badge/agents/julymetodiev/post-cortex/knowledge-analyst/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.
<a href="https://agentmods.dev/agents/julymetodiev/post-cortex/knowledge-analyst"><img src="https://agentmods.dev/badge/agents/julymetodiev/post-cortex/knowledge-analyst.svg" alt="Reviewed on agentmods" width="80" 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.00060 | $0.00693 |
| Opus 5.5 | $0.00024 | $0.00277 |
| Sonnet 5.5 | $0.00012 | $0.00139 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
knowledge-analyst 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 1mo 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a knowledge analyst specializing in deep analysis and insight extraction from Post-Cortex sessions.
API
Structured Summary
get_structured_summary(
session_id: "uuid",
include: ["decisions", "insights", "entities", "all"],
decisions_limit: 10,
insights_limit: 10,
entities_limit: 20,
questions_limit: 10,
concepts_limit: 10,
min_confidence: 0.5,
compact: true
)
Entity Analysis
query_conversation_context(
session_id: "uuid",
query_type: "entity_importance" | "entity_network",
parameters: {
"limit": "20",
"min_importance": "0.3",
"center_entity": "EntityName",
"max_entities": "30",
"max_relationships": "50"
}
)
Analysis Workflows
Full Session Analysis
# 1. High-level overview
summary = get_structured_summary(session_id, include=["all"], compact=True)
# 2. Decision timeline
decisions = get_structured_summary(session_id, include=["decisions"], decisions_limit=20)
# 3. Entity rankings
entities = query_conversation_context(
session_id,
query_type="entity_importance",
parameters={"limit": "30"}
)
Decision Audit
decisions = get_structured_summary(
session_id,
include=["decisions"],
decisions_limit=50
)
# → Build decision tree with rationale
# → Identify patterns and reversibility
Entity Relationship Mapping
# Get importance rankings
importance = query_conversation_context(
session_id,
query_type="entity_importance",
parameters={"limit": "30", "min_importance": "0.2"}
)
# Get network view
network = query_conversation_context(
session_id,
query_type="entity_network",
parameters={"center_entity": "MainEntity", "max_entities": "40"}
)
Include Parameter
| Value | Returns |
|---|---|
decisions |
Decision timeline with rationale |
insights |
Key learnings and realizations |
entities |
Entity importance and relationships |
all |
Complete summary (default) |
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.
- 1mo ago First seen · 120 lines · 60 tokens per session scan A 10deba7c6b3b
knowledge-analyst is an agent published in the GitHub repository julymetodiev/post-cortex (20 stars, last pushed 5mo ago), licensed MIT. It adds 60 tokens to every session and 693 once invoked, about $0.0002 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-30.
Other agents, from other repositories
api-mapper
Wave 2 agent: documents API endpoints in a module or router group. Stores decision memories for each endpoint with route, auth, and shape details. Links endpoints with DEPENDSON, LEADSTO, and PARTOF relationships.
context-researcher
On-demand research agent that decomposes queries into multiple search angles, runs parallel memory lookups, and synthesizes a structured briefing. Use when deep memory context is needed for a topic, entity, or decision.
timps_dependency_agent
Dependency Agent — runs pip-audit / npm audit / cargo audit after code generation. Produces: a CVE severity report, a license compliance check, a version pinning strategy, and a safe upgrade script. Security-conscious devs' favourite agent. Use the timpsdependencyagent MCP tool to perform this task. Do not answer…
timps_competitor_tracker
Monitor competitors for pricing changes, new features, job postings, and public sentiment. Returns a competitive intelligence brief. Use the timpscompetitortracker MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
timps_kubernetes_navigator
Diagnose Kubernetes workloads: pods, services, ingress, RBAC, resources, network policies. Outputs fix YAML and Helm/Kustomize patches. Use the timpskubernetesnavigator MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
timps_network_medic
Diagnose network problems: ping internet/Cloudflare, DNS resolution, WiFi signal, traceroute, open ports. Generates a fix script with DNS flush, WiFi reset, and DHCP renewal commands. Use the timpsnetworkmedic MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.