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 aksika/abtars --skill read-messagesgit clone --depth 1 https://github.com/aksika/abtarsWrote 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/aksika/abtars/read-messages)<a href="https://agentmods.dev/skills/aksika/abtars/read-messages"><img src="https://agentmods.dev/badge/skills/aksika/abtars/read-messages.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00022 | $0.00344 |
| Opus 5 | $0.00011 | $0.00172 |
| Sonnet 5 | $0.00004 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
read-messages 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.
What it actually says
Read Messages
Full documentation for abmind messages. Read-only command — safe against a live gateway (WAL concurrent read), never writes.
List sessions (find the right session_id first)
abmind messages
Output: session_id msgs last per session, newest activity first. Telegram sessions look like telegram:<chatId>.
Dump recent messages of a session
abmind messages --session telegram:111 [--tail 50] [--json] [--raw]
- Default: last 30 messages, newest first, content truncated to 500 chars and secret-redacted
--tail N: how many messages (e.g. 100)--json: machine-readable JSON (id, role, content, timestamp, time)--raw: skip secret redaction — only when the user explicitly needs verbatim content
When to use
- User asks "do you remember what I said 5 minutes ago?" and recent context seems missing
- Suspected hydration/context failure — verify the messages actually reached the DB
- Recovery after a faulty session: read back what was said and continue manually
- Debugging: check whether a turn was recorded at all (message ids, timestamps)
When NOT to use
- Memory search (facts/decisions) → use the
memory-searchskill (abmind recall) - Reading memory contents → that is
abmind recall, not the messages table
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 · 38 lines · 22 tokens per session scan A 15d345c5a707
read-messages is a skill published in the GitHub repository aksika/abtars (9 stars, last pushed today), licensed Apache-2.0. It adds 22 tokens to every session and 344 once invoked, about $0.0001 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-05.
Other skills, from other repositories
context-degradation
This skill should be used for diagnosing and mitigating context degradation: lost-in-middle failures, context poisoning, context clash, context confusion, attention-pattern issues, and agent performance degradation caused by accumulated or conflicting context.
pipeline-validator
Discovers, triggers, and monitors Azure DevOps pipelines (PR, Buddy Build, Buddy Release) for the current repo and branch. Auto-diagnoses failures from build logs, applies fixes, commits, pushes, and re-triggers until all pipelines pass or max retries reached. Validates PR existence and description completeness.…
ai-agents-empirical-probe-toolkit
Prove-it methods for this repo. Six recipes for runtime-contract probes, guard and threshold calibration, eval A/B, docs-vs-reality audits, reproduce-on-main CI triage, and negative-control test design, each with a worked example from repo history. Use when you say probe the runtime contract, calibrate this guard…
memory-enhancement
Manage memory citations, verify code references, and track confidence scores. Use when adding citations to memories, checking memory health, or verifying code references are still valid. Use when you say "add a citation", "verify this memory's code refs", "check memory health". Do NOT use for searching or creating…
research-and-incorporate
Research external topics, create comprehensive analysis, and incorporate learnings into Serena and Forgetful memory systems. Use when you say "research and incorporate {topic}", "study {topic} and add to memory", "deep dive on {topic}", or "learn about {topic} for the project". Works on external concepts, frameworks…
memory-reflexion
Tier 2 episode extraction, the reflexion write path split out of the memory router per ADR-063. Extracts an episode from a completed session log so later sessions can replay what was tried and what it cost. Use when you say extract episode from session, record what happened this session, or re-extract this episode. Do…