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 agentmods add skills/mehboobali98/rmine/clinpx skills add mehboobali98/rmine --skill cligit clone --depth 1 https://github.com/mehboobali98/rmineWrote 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/mehboobali98/rmine/cli)<a href="https://agentmods.dev/skills/mehboobali98/rmine/cli"><img src="https://agentmods.dev/badge/skills/mehboobali98/rmine/cli.svg" alt="Measured on agentmods" 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 | $0.00053 | $0.04517 |
| Opus 5 | $0.00026 | $0.02259 |
| Sonnet 5 | $0.00011 | $0.00903 |
| Haiku 4.5 | $0.00005 | $0.00452 |
Grade A, and why
rmine 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 4d 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reference
Generated by rmine skill install — don't hand-edit, rerun the command
instead after upgrading rmine.
Setup and profiles
rmine needs a profile before anything else works: rmine config init
(interactive; prompts for server URL + API key, or reads $RMINE_URL and
$RMINE_API_KEY when set, for unattended setup). Multiple servers: rmine config add-profile <name>, rmine config use-profile <name> (persistent
switch), rmine --profile <name> ... or RMINE_PROFILE=<name> (one-off
override, flag beats env beats the configured current profile), rmine config list-profiles.
Default project
A profile may carry a default project (rmine config set-default-project "X"), which supplies --project wherever it is omitted: on issue create,
and as the scope for issue list and time list.
time list --issue <id> is not scoped by the default — naming an issue
already determines the project, so the default would only ever contradict it.
A listing without --project may therefore be narrower than it looks.
When the default takes effect rmine says so on stderr — read that line before
reporting a result as "everything there is". To search across all projects
regardless, pass --all-projects; combining it with --project is an error.
rmine config list-profiles shows whether a default is set.
Output format
Default output is a human-readable table. Pass -o json (long form
--output json) on any command when
you intend to parse the result programmatically — always prefer this over
scraping table output.
-o json works on every command, including the ones that change
something: those return {"status": "...", "issue": 1234} (or time_entry,
relation, profile, path), so a write can be confirmed by parsing rather
than by matching English. Empty lists come back as [], never null. Prompts
and warnings go to stderr, so stdout is always parseable on its own.
Failures are JSON too. Under -o json, stdout carries
What ships with it
28 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.
- action_test.go 3.0 KB
- agentgaps_test.go 15 KB
- assignee_test.go 4.5 KB
- config.go 8.1 KB
- defaultproject_test.go 8.6 KB
- docs_test.go 3.4 KB
- enumerations.go 3.2 KB
- issue_test.go 13 KB
- issue_view_test.go 3.6 KB
- issue.go 43 KB
- jsonerror_test.go 5.7 KB
- output_test.go 2.0 KB
- output.go 3.2 KB
- project.go 4.9 KB
- root.go 6.0 KB
- schedule_test.go 2.7 KB
- setup_test.go 2.7 KB
- skill_test.go 6.6 KB
- skill.go 5.5 KB
- smoke_test.go 6.1 KB
- sort_test.go 1.5 KB
- time.go 8.4 KB
- timelog_test.go 3.2 KB
- update_test.go 4.4 KB
- url_test.go 2.3 KB
- version_test.go 1.9 KB
- version.go 1.4 KB
- whoami.go 571 B
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.
- 4d ago First seen · 325 lines · 53 tokens per session scan A da968673d7b4
rmine is a skill published in the GitHub repository mehboobali98/rmine (2 stars, last pushed 11d ago), licensed MIT. It adds 53 tokens to every session and 4,517 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
repo-recap
Generate a comprehensive repo recap (PRs, issues, releases) for sharing with team. Pass "en" or "fr" as argument for language (default fr).
papercut
Capture or triage small Neva repository and engineering-harness frictions without derailing feature work.
skip-test-with-issue
Skip a flaky or broken test with proper issue tracking. Use when asked to skip a test, disable a test, or mark a test as flaky.
kanban-md
Manage project tasks using kanban-md, a file-based kanban board CLI. Use when the user mentions tasks, kanban, board, backlog, sprint, project management, work items, priorities, blockers, or wants to track, create, list, move, edit, or delete tasks. Also use for standup, status update, sprint planning, triage, or…
kanban-based-development
Autonomous, parallel-safe development workflow using kanban-md. Use when the user asks to work through tasks, do kanban-based development, or when multiple agents need to coordinate work on the same codebase. Optimized for explicit handoffs and a "defer to user" protocol when human intervention is required.