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 ebizsoft/agentic-claude-code --skill issue-memorygit clone --depth 1 https://github.com/ebizsoft/agentic-claude-codeWrote 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/ebizsoft/agentic-claude-code/issue-memory)<a href="https://agentmods.dev/skills/ebizsoft/agentic-claude-code/issue-memory"><img src="https://agentmods.dev/badge/skills/ebizsoft/agentic-claude-code/issue-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/ebizsoft/agentic-claude-code/issue-memory"><img src="https://agentmods.dev/badge/skills/ebizsoft/agentic-claude-code/issue-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.00201 | $0.01890 |
| Opus 5.5 | $0.00080 | $0.00756 |
| Sonnet 5.5 | $0.00040 | $0.00378 |
| Haiku 4.5 | $0.00020 | $0.00189 |
Grade A, and why
issue-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 2mo 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issue-memory — GitHub issues as durable agent memory
A stateless agent forgets everything between sessions. This pattern gives it a durable, GitHub-native memory that survives context resets and hands off cleanly between sessions and between agents: one pinned issue per repo, titled "Project log", that any agent reads first and updates last.
The skill is an installer + reference, not a runtime. It does not "run" during a work
session. It (a) seeds a repo with the labels, the pinned log, and a CLAUDE.md conventions
block (scripts/bootstrap.sh), and (b) documents the conventions so agents apply them.
The enforcement mechanism is the target repo's CLAUDE.md — that file is auto-loaded
every session, so the rituals below only actually happen if the conventions section lives
there. templates/claude-md-section.md is that section; bootstrap prints it to append.
What the Project log is (and is not)
One issue per repo, titled "Project log", pinned, labelled agent-context +
decision. It holds three things and nothing else:
- A numbered decision register — every decision that overrides the spec, handoff, or docs, recorded before or with the code that depends on it.
- A current-state summary — where the project is right now, at summary altitude.
- An open-decisions list — what is blocked on a human, cross-referencing
needs-decisionissues.
It is not a changelog and not a work tracker. See "Log altitude" below.
The two rituals
These live in the target repo's CLAUDE.md so every session inherits them.
- Session start: run
gh issue list --state openand read the pinned Project log issue before writing any code. That is the state of the world; specs and docs are older than it. - Session end: comment on every issue you touched with what is done and what is
half-finished, so the next session sees exactly where to resume. Close issues with
Closes #Nin commit messages — never by hand, so the close is tied to the commit that did the work.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 142 lines · 201 tokens per session scan A a2146220c169
issue-memory is a skill published in the GitHub repository ebizsoft/agentic-claude-code (2 stars, last pushed 3mo ago), licensed MIT. It adds 201 tokens to every session and 1,890 once invoked, about $0.0008 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, source notes, 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…