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 kalpmodi/akira --skill compactgit clone --depth 1 https://github.com/kalpmodi/akiraWrote 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/kalpmodi/akira/compact)<a href="https://agentmods.dev/skills/kalpmodi/akira/compact"><img src="https://agentmods.dev/badge/skills/kalpmodi/akira/compact/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/kalpmodi/akira/compact"><img src="https://agentmods.dev/badge/skills/kalpmodi/akira/compact.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.00060 | $0.01081 |
| Opus 5.5 | $0.00024 | $0.00432 |
| Sonnet 5.5 | $0.00012 | $0.00216 |
| Haiku 4.5 | $0.00006 | $0.00108 |
Grade A, and why
compact 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compact - Context Compaction
Overview
Long engagements burn context fast. This skill compresses completed phase outputs
into a single engagement_summary.md without losing any certified intelligence.
Rule: session.json is always the authoritative source of truth.
After compaction, the AI re-reads session.json instead of relying on conversation history.
When to Trigger
Auto-trigger at these moments:
- After completing any full phase (recon, secrets, exploit, zerodayhunt)
- When
session.json signals[]exceeds 30 entries - When the user asks explicitly
- Before spawning a new fork (give the fork a clean context budget)
Steps
-
Get target:
TARGET=$1 SESSION=~/pentest-toolkit/results/$TARGET/session.json RESULTS=~/pentest-toolkit/results/$TARGET -
Identify completed phases:
ls $RESULTS/interesting_*.md 2>/dev/null -
For each completed phase - compress to 5 bullet signals:
Read each
interesting_<phase>.mdand distill to essential intelligence only:RECON SIGNALS (from interesting_recon.md): - Live hosts: <N> discovered, key: <most interesting> - Tech stack: <comma-separated confirmed tech> - WAF: <vendor or null> - Key endpoints: <top 3> - Hypothesis calibration: H1 <N>%, H2 <N>% SECRETS SIGNALS (from interesting_secrets.md): - Credentials found: <Y/N>, type: <aws_key|jwt|password> - Key files: <source locations> - Cloud provider confirmed: <Y/N> EXPLOIT SIGNALS (from interesting_exploit.md): - Confirmed findings: <N>, classes: <list> - SSRF vectors: <Y/N>, endpoints: <list> - Potential findings: <N> -
Write
engagement_summary.md:cat > $RESULTS/engagement_summary.md << EOF # Engagement Summary: $TARGET Compacted: $(date +%Y-%m-%d\ %H:%M) Source of truth: session.json ## Phase Intelligence (Compressed) <5-bullet summaries per completed phase> ## Active Hypotheses <from session.json hypotheses[] - all active ones with current probability> ## Confirmed Findings <from session.json report_draft.findings[] - title + severity + status per finding> ## Open Discovery Queue <from session.json discovery_queue[] - surface + priority per item> ## Signal Summary Total signals: <N> Critical signals: <list VULN_CONFIRMED + CRED_FOUND entries> ## Next Recommended Action <based on engagement_state and top hypothesis probability> EOF
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 · 122 lines · 60 tokens per session scan A d35440ef0c40
compact is a skill published in the GitHub repository kalpmodi/akira (23 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 1,081 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-30.
Other skills, from other repositories
ai-17-memory-chain
Memory injection across conversations, prompt chain manipulation, context poisoning, session memory extraction.
mem0-vercel-ai-sdk
Mem0 provider for Vercel AI SDK (@mem0/vercel-ai-provider). TRIGGER when: user mentions "vercel ai sdk", "@mem0/vercel-ai-provider", "createMem0", "retrieveMemories", "addMemories", "getMemories", "searchMemories", "mem0 vercel", "AI SDK provider", "AI SDK memory", or is using generateText/streamText with mem0. Also…
pause
Pause Mem0 memory capture on this machine. Use when the user wants to stop memories being recorded, for example for private work or experiments.
mine
Mine a project or conversation into your MemPalace — extract and store memories for later retrieval.
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…
mempalace-recall
Recall protocol for MemPalace — search the palace before answering about past work, people, projects, or prior decisions. Apply when the user asks what was decided, what happened before, who someone is, what was discussed last time, or anything that may already be filed in their memory palace; or when mempalace-recall…