context-manager

An agent that records a project's dependencies, coding patterns, conventions, architecture, and important decisions as shared project knowledge. A knowledge graph maps relationships between these parts of a codebase.

In plain words
What is it for?
Use it to document project context, track dependencies, record patterns, map architecture, and produce dependency or convention reports.
Why use it?
It reduces repeated discovery and helps work across sessions stay consistent with the existing project.

Agent

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.

agentmods
npx agentmods add agents/pixel-process-ug/superkit-agents/context-manager
Clone the repo
git clone --depth 1 https://github.com/Pixel-Process-UG/superkit-agents
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 283 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00026 $0.00283
Opus 5 $0.00013 $0.00142
Sonnet 5 $0.00005 $0.00057
Haiku 4.5 $0.00003 $0.00028

Measured yesterday against content hash 2583d4984b2c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

context-manager 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 yesterday.

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.

templates/agents/context-manager.md · 38 lines

What it actually says

Context Manager Agent

You are a context manager maintaining comprehensive project knowledge.

Responsibilities

  1. Dependency Mapping — Track all project dependencies, their versions, and purposes
  2. Pattern Registry — Document coding patterns, naming conventions, and architectural decisions
  3. Codebase Knowledge Graph — Map relationships between modules, services, and data flows
  4. Convention Enforcement — Ensure new code follows established patterns

Knowledge Domains

Domain What to Track
Tech Stack Languages, frameworks, build tools, test frameworks
Architecture Monolith/micro, data flow, API boundaries
Conventions Naming, file structure, import order, error handling
Dependencies Package versions, upgrade status, security advisories
Infrastructure Hosting, CI/CD, monitoring, logging
Team Code owners, review requirements, merge policies

Agent Coordination

Dispatch via Agent tool with subagent_type="Explore" for codebase exploration.

Output Format

  • Project context summary (for memory/project-context.md)
  • Pattern documentation (for memory/learned-patterns.md)
  • Dependency audit report
  • Convention compliance check results
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. yesterday First seen · 38 lines · 26 tokens per session scan A 2583d4984b2c

Subscribe to this mod's changes

context-manager is an agent published in the GitHub repository Pixel-Process-UG/superkit-agents (1 stars, last pushed 5mo ago), licensed MIT. It adds 26 tokens to every session and 283 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

web-performance-auditor

Web performance engineer focused on Core Web Vitals, loading, rendering, and network optimization. Use for performance-focused audits, CWV analysis, and identifying structural performance anti-patterns in web applications.

addyosmani/agent-skills · 45 tokens

security-auditor

Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.

addyosmani/agent-skills · 35 tokens

git-detective

Investigate git history to find when and why bugs were introduced, trace changes, and understand code evolution.

helderberto/agent-skills · 26 tokens

code-reviewer

资深 code reviewer,从 correctness、readability、architecture、security 和 performance 五个维度评估变更。用于合并前的 thorough code review。.

vinvcn/addyosmani-agent-skills-zh · 37 tokens

security-auditor

专注于漏洞检测、威胁建模和安全编码实践的 Security engineer。用于 security-focused code review、threat analysis 或 hardening recommendations。.

vinvcn/addyosmani-agent-skills-zh · 38 tokens

OpenAkashic Agent Contribution Guide

에이전트와 사용자가 OpenAkashic에 접근해 개인·공유 작업 메모리를 남기고, 대표 공개 지식을 활용하고, 재사용 가능한 capsule/claim을 승격하는 표준 흐름이다. MCP를 쓰는 에이전트도, skills 문서와 API 토큰만 쓰는 에이전트도 같은 정책을 따른다.

szara7678/OpenAkashic · 0 tokens