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 Rememora/rememora --skill rememora-developergit clone --depth 1 https://github.com/Rememora/rememoraWrote 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/rememora/rememora/rememora-developer)<a href="https://agentmods.dev/skills/rememora/rememora/rememora-developer"><img src="https://agentmods.dev/badge/skills/rememora/rememora/rememora-developer/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/rememora/rememora/rememora-developer"><img src="https://agentmods.dev/badge/skills/rememora/rememora/rememora-developer.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.00564 |
| Opus 5.5 | $0.00024 | $0.00226 |
| Sonnet 5.5 | $0.00012 | $0.00113 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
rememora-developer 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rememora Developer
Use this skill for implementation work on Rememora.
Scope
- Pick up
Ready-For-Devor approved work - Create or resume issue-specific worktrees under
.agents/worktrees/ - Plan before implementing non-trivial ticket work
- Validate changes with
cargo testandcargo clippy - Use Rememora itself for durable memory and session continuity
Runtime Paths
- Locks:
.agents/locks/ - Worktrees:
.agents/worktrees/issue-<issue-number> - File-based memory leftovers:
.agents/agent-memory/ - Shared repo instructions:
AGENTS.md - Claude-native subagent reference:
.claude/agents/rememora-developer.md
Workflow
-
Load context first.
- Run
rememora context --project rememora - If needed, run targeted recall with
rememora search "<query>" --project rememora
- Run
-
Claim work atomically.
- Use
.agents/locks/issue-<issue-number>andtty-$(basename $(tty)) - Do not start work on a ticket that is actively locked by another live terminal
- Use
-
Work in an isolated git worktree.
- Create or resume
.agents/worktrees/issue-<issue-number> - Do not modify the main checkout while doing ticket implementation work
- Create or resume
-
Stay in plan mode until approval for non-trivial ticket work.
- Write the plan in the issue worktree
- Only implement after approval
-
Validate before completion.
- Run
cargo test - Run
cargo clippy
- Run
-
Persist durable knowledge.
- Use
rememora savefor durable decisions, cases, patterns, entities, and preferences - Use session
working_statefor ephemeral in-progress state
- Use
Category Guide
preference: user collaboration preferencesdecision: architecture or implementation tradeoffscase: tricky bugs, gotchas, fixespattern: reusable conventions or test patternsentity: services, APIs, dashboards, integrationsevent: significant project events
When To Defer To Claude-Specific Logic
If you need the full Claude-native ticket workflow, detailed lock recovery behavior, or the exact project board protocol, read .claude/agents/rememora-developer.md.
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 · 64 lines · 60 tokens per session scan A 7c823e9a0fd1
rememora-developer is a skill published in the GitHub repository Rememora/rememora (3 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 564 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-31.
Other skills, from other repositories
rhiza-fix
Read this repo's open issues, triage them, and open one pull request per issue that can be fixed without a judgement call. Issues that need a decision, or that look stale or superseded, are reported with a recommendation rather than guessed at.
implement-issue
Take a GitHub issue from planning to PR, resumable across clarification waits.
gitlab-mr
GitLab merge request operations. ALWAYS use this skill when user wants to: (1) list merge requests, (2) view MR details, (3) create new MRs, (4) approve/merge MRs, (5) checkout MR branches, (6) add notes/comments, (7) rebase MRs.
rhiza-init
Make the current folder a rhiza-managed repo — write the .rhiza/template.yml pointer, add a skeleton and license, open a PR. Supports Python, Rust and Go. Syncs nothing; run /rhiza:update after it merges.
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.