What is wiki-project?

A project-record system for an Obsidian vault, a folder of linked Markdown notes, covering project status, decisions, milestones, meetings, and future ideas.

It is for creating project pages, updating status, logging decisions and meetings, and recording possible future projects.

It keeps project information in a consistent place and separates current status from the historical record of decisions and meetings.

wiki-project — Skill for Claude Code and Codex by pivoshenko

Install

Getting it into your agent

There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.

Made for: Claude Code, 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/pivoshenko/pivoshenko.ai/wiki-project/github.svg)](https://agentmods.dev/skills/pivoshenko/pivoshenko.ai/wiki-project)

Your own site

<a href="https://agentmods.dev/skills/pivoshenko/pivoshenko.ai/wiki-project"><img src="https://agentmods.dev/badge/skills/pivoshenko/pivoshenko.ai/wiki-project/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/pivoshenko/pivoshenko.ai/wiki-project"><img src="https://agentmods.dev/badge/skills/pivoshenko/pivoshenko.ai/wiki-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 855 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.00098	$0.00855
Opus 5	$0.00049	$0.00428
Sonnet 5	$0.00020	$0.00171
Haiku 4.5	$0.00010	$0.00085

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

Security

Grade A, and why

wiki-project 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.

archive/skills/wiki-project/SKILL.md · 45 lines

How it starts

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

Wiki project

Vault: /Users/volodymyr.pivoshenko/Library/Mobile Documents/iCloud~md~obsidian/Documents/Vault

Project lifecycle in the wiki: index page + ADR-lite decision log + meeting log per project, plus a vault-wide ideas list.

Layout

03 PROJECTS/
├── Ideas.md            # one-liner future-project ideas (type: reference)
└── <Project>/
    ├── <Project>.md    # index: pitch, overview, current state (template: 99 TEMPLATES/Project.md)
    ├── Decisions.md    # append-only decision log
    ├── Meetings.md     # append-only meeting log (created on first meeting)
    └── extras          # project-specific notes (reviews, specs, ...)

Flow

Read vault CLAUDE.md + INDEX.md first.
New project -> subfolder + index from 99 TEMPLATES/Project.md + Decisions.md bootstrap: # Decisions heading + one intro line ("Append-only decision log for [[]]. Entry shape: 99 TEMPLATES/Decision Entry.md."). Real project facts (repo URL, status) -> links + status frontmatter.
Status change -> bump status frontmatter + rewrite ## Current state (keep it current-state, not history — history lives in Decisions.md + LOG.md).
Decision -> append 99 TEMPLATES/Decision Entry.md shape to Decisions.md: date, decision, why, alternatives. Newest at bottom. One entry per decision, terse.
Milestone -> rewrite ## Current state + LOG.md line. If a decision drove it, also a Decisions.md entry. No separate milestone artifact.
Meeting -> append 99 TEMPLATES/Meeting Entry.md shape to the project's Meetings.md: date, discussed, outcomes, actions. Newest at bottom. Create Meetings.md on first meeting (same bootstrap style as Decisions.md). Then distill: decisions land in Decisions.md, durable concepts in 02 PERMANENT NOTES, status shifts in ## Current state — the meeting entry is the record, not the destination. Non-project meetings -> 00 INBOX for later routing.
Project idea -> one-liner bullet in 03 PROJECTS/Ideas.md. Idea got substantial (keeps coming back, has a shape) -> graduate: full hub with status: idea, remove the line from Ideas.md.
Asked "state of " -> read index + Decisions.md tail, answer, fix staleness found on the way (with note to user).
Duties: bump updated, INDEX.md (new pages only), LOG.md line.

Read the full file on GitHub · 45 lines

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.

9d ago First seen · 45 lines · 98 tokens per session scan A 9ddf500f645e

Subscribe to this mod's changes

wiki-project is a skill published in the GitHub repository pivoshenko/pivoshenko.ai (4 stars, last pushed 5d ago), licensed MIT. It adds 98 tokens to every session and 855 once invoked, about $0.0005 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.

Project management Writing and docs agents ai ai-agents ai-skills mcp obsidian skills wiki

80-livekit-agents-majiayu000-claude-skill-registr

Create your LiveKit Agents skill from official documentation, then learn to improve it throughout the chapter.

majiayu000/claude-skill-registry · 18 tokens

agent-creation-skill

Procedural guide for creating new agents from templates when project complexity requires delegation.

majiayu000/claude-skill-registry · 0 tokens

agent-creator

Meta-agent for creating new custom agents, skills, and MCP integrations. Expert in agent design, MCP development, skill architecture, and rapid prototyping. Activate on 'create agent', 'new skill', 'MCP server', 'custom tool', 'agent design'. NOT for using existing agents (invoke them directly), general coding (use…

majiayu000/claude-skill-registry · 84 tokens

loom-usage

Meta-orchestration skill for Claude driving loom itself.

cosmix/loom · 15 tokens

curate-collection

Build and maintain a library collection through acquisitions, weeding (deaccessioning), collection assessment, reader advisory, and interlibrary loan coordination. Covers selection criteria, collection development policies, the CREW/MUSTIE method for weeding, usage analysis, and responsive collection management. Use…

pjt222/agent-almanac · 105 tokens

design-on-call-rotation

Design sustainable on-call rotations with balanced schedules, clear escalation policies, fatigue management, and handoff procedures. Minimize burnout while maintaining incident response coverage. Use when setting up on-call for the first time, scaling a team from 2-3 to 5+ engineers, addressing on-call burnout or…

pjt222/agent-almanac · 86 tokens