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.
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.
[](https://agentmods.dev/skills/renaissance-ai-solutions/consistorium/project-state)<a href="https://agentmods.dev/skills/renaissance-ai-solutions/consistorium/project-state"><img src="https://agentmods.dev/badge/skills/renaissance-ai-solutions/consistorium/project-state/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/skills/renaissance-ai-solutions/consistorium/project-state"><img src="https://agentmods.dev/badge/skills/renaissance-ai-solutions/consistorium/project-state.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.00024 | $0.01880 |
| Opus 5 | $0.00012 | $0.00940 |
| Sonnet 5 | $0.00005 | $0.00376 |
| Haiku 4.5 | $0.00002 | $0.00188 |
Grade A, and why
project-state 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 10d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project State — Establish Reality Before Advice
This skill teaches an AI how to use Consistorium to ground its answers in observed local development state rather than assumptions.
When to use
Use this skill whenever the user asks for strategic, architectural, or prioritization advice about their codebase, or when a fresh agent is continuing a task through Consistorium MCP tools.
Examples:
- "What should I work on next?"
- "Is this architecture still correct?"
- "Are we ready to release?"
- "What is happening in this repo?"
- "Give me a project snapshot before I decide."
Workflow
Follow these steps in order. Prefer snapshots and summaries before requesting large raw diffs.
1. Discover the project
Call context_list_projects to see which projects are explicitly configured and whether each is a git repository. Do not guess a project name or path.
2. Get the strategic briefing
For questions like "what is this?", "what happened?", "what is unfinished?", or "what should we do next?", call context_project_briefing next.
That one call returns live git observation, recent commits, short excerpts from allowlisted strategy docs, open tasks, latest handoffs, blockers, recorded decisions, and recommended next actions.
Treat live.* as current repository observation. Treat continuity.* as agent-recorded claims. Each item carries source.claimType (live_observation vs agent_record). If caveats mentions a stale handoff, re-check with context_project_snapshot before acting.
3. Discover the task
Call context_task_list for the selected project. Choose the relevant stable task ID, then call context_task_get for its objective, constraints, next actions, timestamps, provenance, and refreshed repository availability.
4. Find the latest handoff
Call context_handoff_list filtered by project and task ID. Choose the latest relevant handoff by createdAt, then call context_handoff_get for its summary, findings, structured validation, decisions, blockers, next actions, relevant files/commits, and repository state.
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.
- 10d ago First seen · 149 lines · 24 tokens per session scan A 7289ab6c7c47
project-state is a skill published in the GitHub repository Renaissance-AI-Solutions/consistorium (11 stars, last pushed 15d ago), licensed Apache-2.0. It adds 24 tokens to every session and 1,880 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.
Other skills, from other repositories
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.
mem0-vercel-ai-sdk
Mem0 provider for Vercel AI SDK (@mem0/vercel-ai-provider). TRIGGER when: user mentions "vercel ai sdk", "@mem0/vercel-ai-provider", "createMem0", "retrieveMemories", "addMemories", "getMemories", "searchMemories", "mem0 vercel", "AI SDK provider", "AI SDK memory", or is using generateText/streamText with mem0. Also…
pause
Pause Mem0 memory capture on this machine. Use when the user wants to stop memories being recorded, for example for private work or experiments.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
memory-management
Guide the agent to recall, remember, and route durable learning into Memory, Skills, Scheduled Tasks, or Tape.
mnemos
Task-scoped memory lifecycle — typed MnemoGraph prevents lossy context compaction by treating facts/decisions/code-refs/handoffs as distinct node types with per-type eviction policies.