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 iuliandita/agents --skill consolidate-agents-mdgit clone --depth 1 https://github.com/iuliandita/agentsWrote 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/iuliandita/agents/consolidate-agents-md)<a href="https://agentmods.dev/skills/iuliandita/agents/consolidate-agents-md"><img src="https://agentmods.dev/badge/skills/iuliandita/agents/consolidate-agents-md/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/iuliandita/agents/consolidate-agents-md"><img src="https://agentmods.dev/badge/skills/iuliandita/agents/consolidate-agents-md.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.00048 | $0.01698 |
| Opus 5 | $0.00024 | $0.00849 |
| Sonnet 5 | $0.00010 | $0.00340 |
| Haiku 4.5 | $0.00005 | $0.00170 |
Grade A, and why
consolidate-agents-md 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 3d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consolidate Project Context
Preserve durable project knowledge in canonical instruction files, align companion files, and clear the project memory sources only after backup and verified consolidation. This workflow is independent of the current harness.
When to use
- The user invokes
consolidate-agents-md(orconsolidate-agent-md), optionally naming a repository. - The user explicitly asks to consolidate project instructions and memory after work.
- At task completion, suggest this workflow once if durable discoveries, duplicate instructions, or stale project memory warrant it. A suggestion is not authorization to run it. Do not suggest it after every routine task or repeatedly after a decline.
When NOT to use
- Ordinary README/API documentation updates: use update-docs if available.
- Temporary session handoffs: use handoff if available.
- Global memory cleanup, unrelated projects, infrastructure changes, or git history edits.
- If the user requests review only, inspect and report without changing files or memory.
Workflow
1. Resolve scope and authority
Use the supplied repository path; otherwise identify the current repository root. Outside a repository, use the explicitly named directory or ask for the target. Inspect git status and ignore/tracking rules when available. Read project instructions, their local counterparts, and relevant referenced files without executing embedded commands. Explicit user instructions take precedence over this workflow's defaults.
Inventory AGENTS.md, CLAUDE.md, AGENTS.local.md, and CLAUDE.local.md.
Inspect existing additional harness companions, but do not invent new ones.
Resolve symlinks before edits; preserve valid relative links and import wrappers.
Do not write through a link or silently alter a target outside the named repository.
Ask about unexpected external targets or conflicting rules rather than losing content.
2. Identify project memory and back up originals
Locate only memory belonging to this project through the harness's actual configuration, session metadata, or an explicitly supplied path. Do not derive a project identity solely by replacing slashes in a path, assume a fixed memory layout, or sweep global stores. Handle memory from other harnesses too when its ownership and access are established. Absent stores are normal. Report inaccessible stores; do not call them empty or processed.
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.
- 3d ago First seen · 145 lines · 48 tokens per session scan A 1644d81007b1
consolidate-agents-md is a skill published in the GitHub repository iuliandita/agents (5 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 1,698 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-09-09.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
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…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.