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.
npx skills add 1999AZZAR/project-guardian-mcp-server --skill guardian-memorygit clone --depth 1 https://github.com/1999AZZAR/project-guardian-mcp-serverWrote 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/1999azzar/project-guardian-mcp-server/guardian-memory)<a href="https://agentmods.dev/skills/1999azzar/project-guardian-mcp-server/guardian-memory"><img src="https://agentmods.dev/badge/skills/1999azzar/project-guardian-mcp-server/guardian-memory/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/1999azzar/project-guardian-mcp-server/guardian-memory"><img src="https://agentmods.dev/badge/skills/1999azzar/project-guardian-mcp-server/guardian-memory.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.00043 | $0.01801 |
| Opus 5.5 | $0.00017 | $0.00720 |
| Sonnet 5.5 | $0.00009 | $0.00360 |
| Haiku 4.5 | $0.00004 | $0.00180 |
Grade A, and why
guardian-memory 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.
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guardian Memory
Purpose
Every project interaction creates knowledge. This skill ensures nothing is lost. Use Project-Guardian MCP tools to maintain a living knowledge graph of your project in memory.db. Every write also mirrors automatically into the central aggregate at ~/memory/memory.db, so context stays available across projects; call sync_central_memory to force a sync on demand.
Safety
- Never store credentials, tokens, private keys, or sensitive personal data in observations.
- Ask before any operation that installs hooks, modifies repository files, consolidates databases, or deletes source databases.
- Record significant work only; skip trivial reads, formatting, and transient details.
Quick Start
1. Initialize Project (First Use Only)
initialize_memory
initialize_memory creates the database schema for the active project and ensures the central memory at ~/memory/memory.db exists. It no longer installs hooks or consolidates databases: use setup_pre_commit (with user approval) for hooks, and leave GUARDIAN_AUTO_MERGE unset to keep sub-project databases separate.
If the session started outside the project directory, call set_project_root with the absolute project path first so memory is written to the right project.
Then create the project root entity:
create_entity entities=[{
"name": "project:<project-name>",
"entityType": "project",
"observations": [
"[INIT] Project created | repo: <repo-url> | stack: <tech-stack>",
"[CONTEXT] <brief description of project goals>"
]
}]
2. On Every Session Start
Search for entities related to the current project, directory, file, or topic:
search_nodes query="<file-or-topic>"
Use open_node for exact entities. Use read_graph only when the graph is known to be small or the user explicitly requests a complete view.
3. During Work — Track Everything
After every significant action, record it:
add_observation observations=[{
"entityName": "project:<name>",
"contents": ["[<timestamp>] action: <what> | impact: <effect> | files: <list>"]
}]
What ships with it
3 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.
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 · 159 lines · 43 tokens per session scan A cadb066410db
guardian-memory is a skill published in the GitHub repository 1999AZZAR/project-guardian-mcp-server (3 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 1,801 once invoked, about $0.0002 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.
Other skills, from other repositories
memora
Use when working with persistent memory across sessions, storing/retrieving knowledge, managing TODOs/issues, or when context from previous sessions would be helpful.
import-spreadsheet
Import rows from a CSV or Excel file into a Taskade project (leads, contacts, jobs, products, inventory), skip duplicates, and fill custom fields. Use when the user says "import this spreadsheet into Taskade", "add these leads to my CRM", "load this CSV into my app", or attaches a CSV or XLSX and names a Taskade…
app-report
Build a short status report from the user's Taskade projects (jobs, leads, invoices, tasks) and automations, with counts, what changed, what is overdue, which automations failed, and who owns it. Use when the user asks for "a weekly report", "status of my Taskade workspace", "how is my pipeline", "what is overdue"…
plan-new-app
Plan a new Taskade Genesis app from a business goal, create its data projects and its AI agent in Taskade, and write the build prompt for Taskade EVE. Use when the user says "build me an app in Taskade", "I need a CRM / client portal / booking system / dashboard", "plan a Taskade app", or describes a business process…
getting-started
Connect Taskade and show the user what they can do with it. Use when the user says "set up Taskade", "connect Taskade", "what can you do in Taskade", "what is in my Taskade workspace", or when a Taskade tool fails with a sign-in or plan error.
wenlan-handoff
End a work session. Stores durable captures, writes a narrative session log, and automatically applies typed item-level deltas to the current Space Brief. Invoked as /wenlan-handoff.