guardian-tracker

guardian-tracker is a skill for Codex from 1999AZZAR/project-guardian-mcp-server. It costs 58 tokens per session (1,350 once invoked), scanned A, original, MIT.

An automatic record-keeping skill for software projects. It stores file changes, code edits, decisions, and bug fixes in a memory database called memory.db.

In plain words
What is it for?
Use it after edits, commits, bug fixes, refactoring, and architecture decisions to update file records and link them to relevant project features.
Why use it?
It removes the need to document every important change manually and helps keep project history connected to the files and features involved.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it after edits, commits, bug fixes, refactoring, and architecture decisions to update file records and link them to relevant project features.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/1999azzar/project-guardian-mcp-server/guardian-tracker
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 1999AZZAR/project-guardian-mcp-server --skill guardian-tracker
Clone the repo
git clone --depth 1 https://github.com/1999AZZAR/project-guardian-mcp-server

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.

agentmods badge for guardian-tracker

README.md
[![agentmods](https://agentmods.dev/badge/skills/1999azzar/project-guardian-mcp-server/guardian-tracker/github.svg)](https://agentmods.dev/skills/1999azzar/project-guardian-mcp-server/guardian-tracker)
Your own site
<a href="https://agentmods.dev/skills/1999azzar/project-guardian-mcp-server/guardian-tracker"><img src="https://agentmods.dev/badge/skills/1999azzar/project-guardian-mcp-server/guardian-tracker/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.

agentmods 80×15 button for guardian-tracker

Your own site · 80×15
<a href="https://agentmods.dev/skills/1999azzar/project-guardian-mcp-server/guardian-tracker"><img src="https://agentmods.dev/badge/skills/1999azzar/project-guardian-mcp-server/guardian-tracker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,350 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00058 $0.01350
Opus 5 $0.00029 $0.00675
Sonnet 5 $0.00012 $0.00270
Haiku 4.5 $0.00006 $0.00135

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

Security

Grade A, and why

guardian-tracker 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.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/track_changes.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/guardian-tracker/SKILL.md · 167 lines

How it starts

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

Guardian Tracker — Auto-Track Skill

Purpose

Manually tracking every change is tedious. This skill automates it. After every significant operation, it analyzes what changed and records it to memory.db via Project-Guardian MCP tools.

When to Load

  • After file edits or creates
  • After git commits
  • After bug fixes
  • After refactoring
  • After architectural decisions
  • At end of significant work blocks

Core Workflow

After File Edit/Create

  1. Identify what changed (new file? modified? which functions?)
  2. Check if file entity exists:
    search_nodes query="file:<path>"
    
  3. Create a missing file entity with create_entity; update an existing one with add_observation:
     add_observation observations=[{
       "entityName": "file:<path>",
       "contents": ["[<timestamp>] action: edit | changes: <summary> | lines: +/-<count>"]
    }]
    
  4. Link to relevant features/tasks:
    create_relation relations=[{
      "from": "file:<path>",
      "to": "feature:<name>",
      "relationType": "implements"
    }]
    

After Git Commit

  1. Run the bundled tracker to obtain machine-readable changed and untracked paths
  2. Create/update entities for each changed file
  3. Create a task observation for the commit:
    add_observation observations=[{
      "entityName": "project:<name>",
      "contents": ["[<timestamp>] commit: <hash> | message: <msg> | files: <count>"]
    }]
    
  4. Link changed files to the commit's purpose

After Bug Fix

  1. Create bug entity:
    create_entity entities=[{
      "name": "bug:<id>:<slug>",
      "entityType": "bug",
      "observations": [
        "[<timestamp>] reported: <error> | severity: <level>",
        "[<timestamp>] cause: <root cause>",
        "[<timestamp>] fix: <solution> | files: <list>"
      ]
    }]
    
  2. Link bug to affected entities:
    create_relation relations=[{
      "from": "bug:<id>:<slug>",
      "to": "task:<id>",
      "relationType": "blocks"
    }]
    
  3. After fix, remove blocks relation:
    delete_relation relations=[{
      "from": "bug:<id>:<slug>",
      "to": "task:<id>",
      "relationType": "blocks"
    }]
    

Read the full file on GitHub · 167 lines

Files

What ships with it

2 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.

  1. 10d ago First seen · 167 lines · 58 tokens per session scan A d812302edfe8

Subscribe to this mod's changes

guardian-tracker is a skill published in the GitHub repository 1999AZZAR/project-guardian-mcp-server (3 stars, last pushed 10d ago), licensed MIT. It adds 58 tokens to every session and 1,350 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.

Related

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.

agentic-box/memora · 33 tokens

vault

Search, read, write, and manage files in the Kept conversation vault. Use when the user asks about past conversations, wants to save notes, needs to find specific content, or wants to organize their vault.

egroup-labs/kept · 45 tokens

searxng-kg-ingestion

Persist SearXNG search results into the epistemic-graph knowledge graph via the searxng-mcp MCP server. Use when the agent must turn a web search into durable, semantically-searchable KG memory — each result becomes a :Document (plus :SearchQuery and :SearchEngine typed nodes with :resultOf / :fromEngine links) so…

Knuckles-Team/searxng-mcp · 126 tokens

codemem

Quick reference for all 32 codemem MCP tools. Use when working with the codemem knowledge graph — finding code, traversing relationships, storing memories, or running analysis.

cogniplex/codemem · 41 tokens

post-cortex-agents

Multi-agent orchestration system for Post-Cortex MCP memory infrastructure. Use when working with persistent memory, knowledge graphs, semantic search, session management, or context building.

julymetodiev/post-cortex · 39 tokens

omni-context-memory

Use the user's Omni-Context long-term memory when it is connected over MCP. Trigger this whenever you need to recall what the user has done, decided, or prefers across past conversations, or when a conversation reaches something worth remembering. Omni-Context is a local knowledge graph — NOT the standard…

guo6x/Omni-context · 96 tokens