Borrowing it
Nothing to install: this file belongs to RooAGI/Lint-AI. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/RooAGI/Lint-AI/main/.claude/skills/lint-ai-memory/SKILL.mdgit clone --depth 1 https://github.com/RooAGI/Lint-AIWrote 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/rooagi/lint-ai/lint-ai-memory)<a href="https://agentmods.dev/skills/rooagi/lint-ai/lint-ai-memory"><img src="https://agentmods.dev/badge/skills/rooagi/lint-ai/lint-ai-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/rooagi/lint-ai/lint-ai-memory"><img src="https://agentmods.dev/badge/skills/rooagi/lint-ai/lint-ai-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.00031 | $0.00670 |
| Opus 5 | $0.00015 | $0.00335 |
| Sonnet 5 | $0.00006 | $0.00134 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
lint-ai-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 10d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lint-AI Memory
MCP-first memory policy
For requests about project history, prior decisions, architectural choices,
earlier work, or "why" something was implemented, the first tool call must be
mcp__lint-ai__search. Do not begin with Bash, Read, repository search, or
another memory system for those requests.
Use this sequence:
- Call
mcp__lint-ai__searchwith a concise query describing the missing context. - Use the returned results as context and distinguish retrieved facts from current source facts.
- Check cited files only after the MCP search, and only when the answer also requires current source details.
- Prefer exact-revision or clearly relevant results and state uncertainty when the results are incomplete.
Use mcp__lint-ai__info only to check MCP workspace status or diagnose the
server. It is not a memory search and should not replace search.
Explicit session recording
Session recording is off by default until the user enables Lint-AI. Enabling
Lint-AI also starts recording by default. Users can explicitly override this
with mcp__lint-ai__record_session and {"action":"stop"}. Recording is
capture-only: it records redacted lifecycle events locally and does not inject
memory into the session.
When the user asks to stop recording, call the same tool with
{"action":"stop"}. Use {"action":"status"} only when the user asks
whether recording is active. Never start recording implicitly for ordinary
memory searches or project work.
Lint-AI memory controls
When the user explicitly asks to turn Lint-AI memory off, call
mcp__lint-ai__disable_lint_ai. When the user asks to turn it back on, call
mcp__lint-ai__enable_lint_ai. These controls affect future Lint-AI retrieval
and memory capture. Enabling memory also starts recording by default, while
disabling memory leaves the recording choice unchanged. Use
mcp__lint-ai__lint_ai_status when the user asks whether memory behavior is
enabled. Do not toggle memory implicitly during a task.
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.
- 10d ago First seen · 65 lines · 31 tokens per session scan A a4351a037d33
lint-ai-memory is a skill published in the GitHub repository RooAGI/Lint-AI (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 31 tokens to every session and 670 once invoked, about $0.0002 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.
Other skills, from other repositories
aikito
Install, configure, and operate Aikito workspaces, including memory, skills, project resources, MCP servers, subagents, adoption, synchronization, and status verification.
openlore
Query and publish to an OpenLore knowledge base over SSH using ordinary shell commands. Use when a task needs project documentation, runbooks, shared team knowledge, or a place to publish findings.
openlore-housekeeping
Audit and maintain a shared OpenLore knowledge base. Use on a schedule or on request to find stale docs, broken links, unreviewed inbox items, and missing skill coverage, then publish an audit report.
durable-memory
Git-versioned memory stored in the Aikito workspace, separate from any Agent's built-in memory. Use to search, retrieve, or persist cross-project and project-scoped durable knowledge, historical decisions, user preferences, or verified architecture constraints.
cortadel
Cortadel is a self-hosted, bi-temporal graph memory server for AI agents — one .NET container exposing a REST API and an MCP endpoint over FalkorDB or Memgraph, with intent-aware writes (store/invalidate/delete-entity/touch/resolve), LLM-verified dedup with a negation guard, and hybrid BM25+vector+RRF retrieval…
forget
Retract or permanently erase a Cortadel memory. Use when the user says "forget that...", "X is no longer true", "that's outdated", "delete this memory", or "permanently remove ". Default path is a natural-language retraction that keeps history queryable; hard, unrecoverable deletion only happens on an explicit…