agentmods.dev

gitmem-status

A status command for GitMem, a memory system for coding agents. It reports whether GitMem is connected, the current session, hook activity, and the audit trail of memory lookups and actions.

In plain words
What is it for?
Use it to inspect the active GitMem session, connection status, hook counts, recall activity, and recent audit entries.
Why use it?
It gives one place to check whether GitMem is working and whether the agent followed the expected memory process. It can also reveal actions taken without a preceding memory lookup.

Command

9 23d ago A scan 12 tokens original MIT
View the source file gitmem-dev/gitmem
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.

agentmods
npx agentmods add commands/gitmem-dev/gitmem/gitmem-status
Clone the repo
git clone --depth 1 https://github.com/gitmem-dev/gitmem
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 439 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00012 $0.00439
Opus 5 $0.00006 $0.00219
Sonnet 5 $0.00002 $0.00088
Haiku 4.5 $0.00001 $0.00044

Measured yesterday against content hash b3040bc640c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gitmem-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 yesterday.

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.

hooks/commands/gitmem-status.md · 49 lines

What it actually says

GitMem Status

Check the current state of the GitMem hooks plugin and active session.

Instructions

  1. Check if gitmem MCP is connected: Call the mcp__gitmem__gitmem-cache-status tool. If it returns a response, the server is connected. Report scar count and cache age from the response. Do NOT use claude mcp list — its health check returns false negatives.

  2. Check active session: Read .gitmem/active-session.json if it exists. Report:

    • Session ID
    • Agent identity
    • Start time
    • Whether scars have been surfaced (surfaced_scars timestamp)

  3. Check hook state: Look for /tmp/gitmem-hooks-* directories. Report:

    • Session start time
    • Tool call count
    • Last nag time
    • Whether stop_hook_active guard is set

  4. Check audit trail: Read /tmp/gitmem-hooks-*/audit.jsonl if it exists. Report:

    • Total LOOKED events (recall/search calls)
    • Total ACTION events (consequential actions)
    • Whether any ACTION was taken without a prior LOOKED (potential gap)
    • Last 5 audit entries

  5. Summary: Present a concise status block:

    GitMem Status
├── MCP Server: connected/disconnected
├── Active Session: <id> (started <time>)
├── Recall: last called <time> / never called
├── Tool Calls: <count>
├── Audit Trail: <looked> LOOKED / <action> ACTION events
│   └── Look-before-act: <yes/gap detected>
└── Hooks: session-start ✓ | recall-check ✓ | post-tool-use ✓ | close-check ✓
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. yesterday First seen · 49 lines · 12 tokens per session scan A b3040bc640c3

Subscribe to this mod's changes

gitmem-status is a command published in the GitHub repository gitmem-dev/gitmem (9 stars, last pushed 23d ago), licensed MIT. It adds 12 tokens to every session and 439 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.

Memory and contextagentic-aiaiai-agentsclaude-codeinstitutional-memorymcp
Related

Other commands, from other repositories

README

Git workflow and quality assurance commands for the claude-skills repository.

alirezarezvani/claude-skills · 0 tokens

agentlas-cloud

Staff a task only from the signed-in owner's Agent Cloud agents.

agentlas-ai/Agentlas-OS · 13 tokens

research-perplexity

Run a deep research query using Perplexity's /research mode via Playwright browser automation. This is an alternative to /export-to-council that uses Perplexity's dedicated research mode instead of multi-model council.

intellegix/intellegix-code-agent-toolkit · 0 tokens

dispatcher

Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.

Kanevry/session-orchestrator · 31 tokens

tldr

Re-apply TLDR rules for this turn (verdict first, no filler).

0p9b/TLDR · 17 tokens

execute

Interactive workflow for workspace isolation, pane-delegated implementation, testing, review, and cleanup.

transparent-pegasus/herdrpowers · 18 tokens