agentmods.dev

issue-tracker

issue-tracker is an agent for coding agents from rebel0789/Memory-Recall. It costs 0 tokens per session (846 once invoked), scanned A, original, Apache-2.0.

Issues and PRDs for this repo live in GitHub Issues for rebel0789/Memory-Recall. Use the gh CLI for canonical issue operations.

Agent

not rated 8 1mo ago A scan 0 tokens original Apache-2.0
View the source file rebel0789/Memory-Recall
Install

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.

agentmods
npx agentmods add agents/rebel0789/memory-recall/issue-tracker
Clone the repo
git clone --depth 1 https://github.com/rebel0789/Memory-Recall

Wrote 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.

agentmods badge for issue-tracker

README.md
[![agentmods](https://agentmods.dev/badge/agents/rebel0789/memory-recall/issue-tracker.svg)](https://agentmods.dev/agents/rebel0789/memory-recall/issue-tracker)
Your own site
<a href="https://agentmods.dev/agents/rebel0789/memory-recall/issue-tracker"><img src="https://agentmods.dev/badge/agents/rebel0789/memory-recall/issue-tracker.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 846 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00846
Opus 5 $0.00000 $0.00423
Sonnet 5 $0.00000 $0.00169
Haiku 4.5 $0.00000 $0.00085

Measured today against content hash a2dbef16312a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

issue-tracker 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 today.

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.

docs/agents/issue-tracker.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Issue tracker: GitHub with local drafts

Issues and PRDs for this repo live in GitHub Issues for rebel0789/Memory-Recall. Use the gh CLI for canonical issue operations.

Local markdown under .scratch/ may be used for offline notes, private scratch work, or draft issue/PRD shaping before publishing to GitHub. Local markdown is not the canonical tracker unless the user explicitly asks for a local-only draft.

GitHub conventions

  • Create an issue: gh issue create --title "..." --body "...". Use a heredoc for multi-line bodies.
  • Read an issue: gh issue view <number> --comments, filtering comments by jq and also fetching labels.
  • List issues: gh issue list --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]' with appropriate --label and --state filters.
  • Comment on an issue: gh issue comment <number> --body "..."
  • Apply / remove labels: gh issue edit <number> --add-label "..." / --remove-label "..."
  • Close: gh issue close <number> --comment "..."

Infer the repo from git remote -v - gh does this automatically when run inside a clone.

Pull requests as a triage surface

PRs as a request surface: yes.

External PRs run through the same labels and states as issues. Collaborator-owned in-flight PRs are not part of the request queue.

Use the gh pr equivalents:

  • Read a PR: gh pr view <number> --comments and gh pr diff <number> for the diff.
  • List PRs for triage: gh pr list --state open --json number,title,author,isDraft,mergeStateStatus,mergeable,statusCheckRollup,labels,headRefName,updatedAt,url. When open issues are empty, inspect open PRs before inventing backlog work. Maintainer-owned CLEAN PRs are release/review queue; bot or external UNSTABLE PRs are triage queue.
  • Detect superseded PRs: compare gh pr diff <number> --name-only with the active branch (git diff --name-only origin/main...HEAD), staged (git diff --cached --name-only), and unstaged (git diff --name-only) file lists before cherry-picking or merging old green PRs into an active branch.
  • Comment / label / close: gh pr comment, gh pr edit --add-label/--remove-label, gh pr close.

Read the full file on GitHub · 52 lines

Changes

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.

  1. today First seen · 52 lines · 0 tokens per session scan A a2dbef16312a

Subscribe to this mod's changes

issue-tracker is an agent published in the GitHub repository rebel0789/Memory-Recall (8 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 846 tokens. 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-04.

Memory and contextWriting and docsagent-memoryai-agentsclaude-codecode-intelligencecodexcursor
Related

Other agents, from other repositories

brain-os-mode

Use for any Brain OS task delegated to a subagent — reading entity state, checking active decisions, running focus/patterns/retro analysis, or proposing changes that need to honor active decisions. Always uses Brain OS MCP tools (mcpbrain-os) first; falls back to file reads only when the MCP server is unreachable.…

brainOS-HQ/brain-os · 97 tokens

OpenAkashic Agent Contribution Guide

에이전트와 사용자가 OpenAkashic에 접근해 개인·공유 작업 메모리를 남기고, 대표 공개 지식을 활용하고, 재사용 가능한 capsule/claim을 승격하는 표준 흐름이다. MCP를 쓰는 에이전트도, skills 문서와 API 토큰만 쓰는 에이전트도 같은 정책을 따른다.

szara7678/OpenAkashic · 0 tokens

Codex AGENTS Template

Copy this text into /.codex/AGENTS.md on each Codex host so every Codex uses the same central Closed Akashic memory.

szara7678/OpenAkashic · 0 tokens

agent

Codex, Cursor, OpenCode and similar agents should treat OpenAkashic as a world-agent shared memory system: a shared working-memory layer plus a reviewed public answer layer, not as a one-shot retrieval dump.

szara7678/OpenAkashic · 0 tokens

Codex AGENTS Template Capsule

본 프로토콜은 모든 Codex 에이전트가 개별적인 로컬 메모리 대신, Closed Akashic Memory (MCP)를 유일하고 중앙화된 장기 작업 메모리로 사용하도록 표준화합니다. 이는 모든 에이전트가 동일한 지식 기반과 작업 흐름을 공유하여 지식의 파편화(fragmentation)를 방지하고, 일관성 있는 지식 관리를 보장하는 것이 핵심 목표입니다.

szara7678/OpenAkashic · 0 tokens

Distributed Agent Memory Contract

Remote agents on different servers should use one shared operating pattern: a world-agent shared memory layer from Closed Akashic over MCP, canonical truth from each project repo, and a tiny per-Codex AGENTS.md that points agents back to this server.

szara7678/OpenAkashic · 0 tokens