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 HITMANdark07/neatcodeai --skill filing-knowledgegit clone --depth 1 https://github.com/HITMANdark07/neatcodeaiWrote 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/hitmandark07/neatcodeai/filing-knowledge)<a href="https://agentmods.dev/skills/hitmandark07/neatcodeai/filing-knowledge"><img src="https://agentmods.dev/badge/skills/hitmandark07/neatcodeai/filing-knowledge/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/hitmandark07/neatcodeai/filing-knowledge"><img src="https://agentmods.dev/badge/skills/hitmandark07/neatcodeai/filing-knowledge.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.00057 | $0.01548 |
| Opus 5.5 | $0.00023 | $0.00619 |
| Sonnet 5.5 | $0.00011 | $0.00310 |
| Haiku 4.5 | $0.00006 | $0.00155 |
Grade A, and why
filing-knowledge 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Filing Knowledge
Overview
Every session that derives a non-trivial structural answer should leave behind a note. The next session — yours, a teammate's, a fresh agent in two months — should look up the answer in .neatcode/memory/ instead of re-running the same five graph queries.
This skill writes Markdown files to .neatcode/memory/<slug>.md. It does not call any neatcode MCP tool — it consumes the result of prior tool calls (typically from exploring-codebase) and persists it.
Trigger
Activate when, in the current turn, ANY of the following is true:
- The answer required more than two graph queries. If you called
query_graph,trace_flow, orfind_nodethree or more times to compose the answer, the next session shouldn't repeat that work. - The answer involved interpretation across multiple files. Reading three files and synthesizing the relationship between them is exactly the kind of thing that compounds — write it down.
- The answer surfaced tribal knowledge. Anything along the lines of "ah, the reason this is shaped this way is..." that wasn't already documented in
REPO_OVERVIEW.md,decisions/, ormemory/. - You shipped a placeholder, stub, or simplification during autonomous work. Examples:
// TODO: real auth wired here,dev-user assumes all scopes,caching disabled until X is decided,magic constant 100 — pick the real number once telemetry exists. The next session needs to know what's pretending to work and what's load-bearing — file the placeholder, not just leave it in code. - You made a load-bearing architectural choice not specified in the prompt. "I picked X over Y because Z" — write it down before the reasoning evaporates. This is most common during autonomous, multi-task runs where the agent makes 5-10 small judgment calls per phase that compound.
If none of these apply, skip. Trivial one-shot answers don't need notes.
The first three triggers cover answering a question. The last two cover autonomous work — file under the same skill since the destination (.neatcode/memory/) is the same. The agent doesn't need permission from the user to surface a filing proposal in autonomous flows; just propose, then continue.
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 · 108 lines · 57 tokens per session scan A f631be0e9862
filing-knowledge is a skill published in the GitHub repository HITMANdark07/neatcodeai (0 stars, last pushed 8d ago), licensed MIT. It adds 57 tokens to every session and 1,548 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
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…