What is project-knowledge-maintainer?

A project knowledge base maintained through AGENTS.md and organized knowledge files. It records a project’s purpose, architecture, decisions, bugs, interfaces, and recent changes for coding agents.

Use it to initialize or update project documentation, preserve bug fixes, record decisions, document APIs or schemas, and organize development notes.

It prevents every new agent session from having to rediscover project context, past fixes, and important technical decisions.

project-knowledge-maintainer — Skill for Codex by chancy24

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 chancy24/codex-knowledge-base-skill --skill project-knowledge-maintainer

Clone the repo

git clone --depth 1 https://github.com/chancy24/codex-knowledge-base-skill

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/chancy24/codex-knowledge-base-skill/project-knowledge-maintainer/github.svg)](https://agentmods.dev/skills/chancy24/codex-knowledge-base-skill/project-knowledge-maintainer)

Your own site

<a href="https://agentmods.dev/skills/chancy24/codex-knowledge-base-skill/project-knowledge-maintainer"><img src="https://agentmods.dev/badge/skills/chancy24/codex-knowledge-base-skill/project-knowledge-maintainer/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/chancy24/codex-knowledge-base-skill/project-knowledge-maintainer"><img src="https://agentmods.dev/badge/skills/chancy24/codex-knowledge-base-skill/project-knowledge-maintainer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,136 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.

Model	Per session	Once invoked
Fable 5.1	$0.00033	$0.01136
Opus 5.5	$0.00013	$0.00454
Sonnet 5.5	$0.00007	$0.00227
Haiku 4.5	$0.00003	$0.00114

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

Security

Grade A, and why

project-knowledge-maintainer 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.

skills/project-knowledge-maintainer/SKILL.md · 143 lines

How it starts

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

Project Knowledge Maintainer

Purpose

Use this Skill to initialize, maintain, and evolve a project-level knowledge base for AI coding agents. The knowledge base helps future agent sessions understand project purpose, architecture, interfaces, decisions, bugs, and recent changes without rediscovering everything from scratch.

Keep the workflow tool-neutral. It should be usable by Codex, Claude Code, Cursor, Gemini CLI, and other coding agents that can read project files and follow repository-local instructions.

When To Use

Use this Skill when the user asks to:

initialize a project knowledge base
summarize or document a project
fix a bug and preserve the repair experience
add or change a feature
add or change an API, schema, command, or data format
record a technical decision or tradeoff
organize raw project materials into structured knowledge
review or retrospect a completed development session
update AGENTS.md or files under knowledge/

Inputs

Common inputs include:

The current repository or target project path.
Existing project files, source code, docs, issues, logs, or raw materials.
The user's current task and any implementation changes made during the session.
Existing AGENTS.md, knowledge/, raw/, or skills/ content if present.

Outputs

Expected outputs include:

AGENTS.md project rules.
knowledge/overview.md project overview.
knowledge/business.md business logic and usage scenarios.
knowledge/architecture.md system architecture and data flow.
knowledge/api.md interfaces, schemas, commands, and data structures.
knowledge/decisions.md technical decisions and tradeoffs.
knowledge/bugs.md bug history, root causes, fixes, and prevention rules.
knowledge/changelog.md session-level change records.
Optional raw/ and project-local skills/ folders.
A short final report listing what was updated and what still needs verification.

Workflow

Read project rules first:
- AGENTS.md if present.
- knowledge/overview.md
- knowledge/architecture.md
- knowledge/decisions.md
- knowledge/bugs.md
If initializing a repository, use the templates in references/templates/ or run the initializer script from this package.
Understand the current task and identify what changed:
- project goal or business logic
- architecture or module boundaries
- API, command, data file, schema, or return structure
- bug symptom, root cause, fix, or prevention rule
- technical decision or tradeoff
- user-facing behavior or UI convention
Update only the relevant knowledge files.
Remove or reconcile duplicate, stale, or contradictory content.
Always update knowledge/changelog.md after important work.
Report the updated files and any missing validation.

Read the full file on GitHub · 143 lines

Files

What ships with it

10 files 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.

1mo ago First seen · 143 lines · 33 tokens per session scan A f5bc37e1cb42

Subscribe to this mod's changes

project-knowledge-maintainer is a skill published in the GitHub repository chancy24/codex-knowledge-base-skill (1 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 1,136 once invoked, about $0.0001 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.

Claude Code Memory and context agent-skill ai-agent codex coding-agents cursor

ctx

Use ctx as working memory for prior agent work. Before starting or continuing work in an unfamiliar area, resuming earlier work, or revisiting an investigation, search prior sessions to ground yourself in earlier context. Use ctx blame to trace a line, file, commit, or PR to the agent session that produced it. Use…

ctxrs/ctx · 106 tokens

karpathy-llm-wiki

Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.

Astro-Han/karpathy-llm-wiki · 67 tokens

source-command-latch-seed

Preview and apply latch seed candidates from the exact current Cursor conversation. Use when the user invokes latch-seed or /latch-seed in Cursor.

open-latch/latch · 37 tokens

imprint

Your habits, imprinted on AI. Learns how you work from conversation, builds a portable profile, and applies judgment that adapts to you: when to act, when to check with you, when to follow the project's rules over your own defaults. Use this skill whenever the user starts a new session, opens a project, writes or…

ilang-ai/Imprint · 108 tokens

learning-retrospective

A skill for saving verified lessons from difficult coding tasks so future agents can use them. It covers both learning after a task succeeds and recalling an existing lesson when the same problem appears again.

Yingqi-Han/learning-retrospective-skill · 64 tokens

krimto-write-fact

Use when the user asks you to remember something for later, save team knowledge, record a decision, or note a durable fact about the project, person, or team. Triggers on "remember that", "save this", "add to memory", "note for the team". Do not use for conversational context.

krimto-labs/krimto · 70 tokens