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 HAR5HA-7663/graphify-starter --skill brain-statusgit clone --depth 1 https://github.com/HAR5HA-7663/graphify-starterWrote 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/har5ha-7663/graphify-starter/brain-status)<a href="https://agentmods.dev/skills/har5ha-7663/graphify-starter/brain-status"><img src="https://agentmods.dev/badge/skills/har5ha-7663/graphify-starter/brain-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.
<a href="https://agentmods.dev/skills/har5ha-7663/graphify-starter/brain-status"><img src="https://agentmods.dev/badge/skills/har5ha-7663/graphify-starter/brain-status.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.00061 | $0.00458 |
| Opus 5.5 | $0.00024 | $0.00183 |
| Sonnet 5.5 | $0.00012 | $0.00092 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
brain-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 29d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 29d ago Changed 37f7dcf026d2
- 1mo ago First seen · 40 lines · 61 tokens per session scan A 674a9041986b
brain-status is a skill published in the GitHub repository HAR5HA-7663/graphify-starter (3 stars, last pushed 29d ago), with no licence file. It adds 61 tokens to every session and 458 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
rag
Reports the state of your brain's search index — the RAG: how many notes and chunks are indexed, whether the live watcher is running, which embedder is in use, and the engine + index-schema versions. Re-indexes on demand too. The front door for the words owners reach for: '/rag', plus 'index status', 'is my index up…
brain
Health-check the second brain so failures are not silent: is the local search server alive, is the RAG index fresh, is the session-memory ledger filling, did the nightly distillation run. Read-only, with a green/red verdict per component. Triggers: "/brain", "/memory", "is the reindex alive".
llm-wiki
Explain and apply the foundational LLM Wiki architecture and knowledge-management strategy. Use for setup, architecture, schema, or organization decisions; operational ingest/query/lint work uses dedicated skills.
llmwiki
Build and use a persistent, citation-traceable knowledge wiki from documents, research papers, notes, or project documentation. Use for llmwiki projects, retrieving reusable evidence for an agent task, or compiling a corpus for repeated questions. A one-off file read or live web search does not need a wiki.
llm-wiki
Build and maintain a persistent, interlinked Obsidian-compatible markdown wiki using Karpathy's LLM Wiki pattern. Extension-backed with auto-generated metadata, guardrails, and 14 custom tools (+3 opt-in agent-trajectory tools).
graphify
Use when the user invokes /graphify or asks to build, update, or query a knowledge graph from a folder of files (code, docs, papers, notes, images). Triggers: 'map this codebase', 'graph my notes', 'what is connected across these files', 'community detection', 'GraphRAG', incremental graph update, Neo4j/SVG/GraphML…