What is project-status?

A briefing tool that summarises the current state of a software project in about 30 seconds. It combines the project’s technology, folders, Git history, recent changes, deployment status, and wiki information.

Use it inside a child project with “project status,” “status briefing,” or “/project-status.” It reports the technology stack, structure, recent work, deployment state, current status, and related wiki page.

It saves time when joining a project or returning to one after a break. The briefing puts the most relevant status details in one place.

How ozgurkarahan/ai-agent-memory configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to ozgurkarahan/ai-agent-memory. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ozgurkarahan/ai-agent-memory/master/.claude/skills/project-status/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/ozgurkarahan/ai-agent-memory

Made for: Claude Code.

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/ozgurkarahan/ai-agent-memory/project-status/github.svg)](https://agentmods.dev/skills/ozgurkarahan/ai-agent-memory/project-status)

Your own site

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

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

When invoked 1,189 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.00055	$0.01189
Opus 5	$0.00028	$0.00594
Sonnet 5	$0.00011	$0.00238
Haiku 4.5	$0.00006	$0.00119

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

Security

Grade A, and why

project-status 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 8d 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.

.claude/skills/project-status/SKILL.md · 102 lines

How it starts

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

Project Status

When the user says "project status", "status briefing", or invokes /project-status from inside any project directory (NOT memory itself), produce a complete situational-awareness briefing so the user can get up to speed on that project in 30 seconds.

This skill is for any child project. When invoked from the memory system itself, refuse and direct the user to the wiki because the wiki is its status.

Coexists with the per-project /status command that ships in every scaffolded project under .claude/commands/status.md. The per-project version is Claude-Code-specific. THIS memory skill is the agent-agnostic version (works under GitHub Copilot CLI, Claude Code, or any tool that loads .github/instructions/). When both are available, prefer the per-project one if you are inside Claude Code (richer integration), otherwise use this skill.

Instructions

Gather information from ALL the sources below, then produce a single structured briefing. Use parallel tool calls to speed up the research.

Resolve the memory root

If the current project contains schema.md or memory/schema.md, it is the memory system or its installer; refuse as described above.
Otherwise follow the memory-wiki path declared in the child project's AGENT.md.
If no memory root resolves, continue the codebase briefing but mark the wiki page as unavailable instead of guessing a personal path.

1. Codebase analysis

Tech stack: languages, frameworks, key dependencies (check package.json, requirements.txt, pyproject.toml, *.csproj, Cargo.toml, go.mod, pom.xml, etc.)
Folder structure: high-level tree (max 2 levels deep), explain what each top-level folder contains
Key files: entry points, config files, main modules
Architecture patterns: monolith/microservices, API style (REST/GraphQL/gRPC), state management, key abstractions
Size: approximate number of source files and lines of code

2. Project history — what we've done

Read the full file on GitHub · 102 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.

8d ago First seen · 102 lines · 55 tokens per session scan A e19a668af34b

Subscribe to this mod's changes

project-status is a skill published in the GitHub repository ozgurkarahan/ai-agent-memory (8 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 1,189 once invoked, about $0.0003 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.

Git and workflow Project management

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

shiplog

Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.

aeonfun/aeon · 46 tokens

llxprt-issue-workflow

Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…

vybestack/llxprt-code · 87 tokens

ai-agent-memory: Skill for Claude Code