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 attebury/remogram --skill remogram-consumergit clone --depth 1 https://github.com/attebury/remogramWrote 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/attebury/remogram/remogram-consumer)<a href="https://agentmods.dev/skills/attebury/remogram/remogram-consumer"><img src="https://agentmods.dev/badge/skills/attebury/remogram/remogram-consumer/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/attebury/remogram/remogram-consumer"><img src="https://agentmods.dev/badge/skills/attebury/remogram/remogram-consumer.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.00047 | $0.01892 |
| Opus 5.5 | $0.00019 | $0.00757 |
| Sonnet 5.5 | $0.00009 | $0.00378 |
| Haiku 4.5 | $0.00005 | $0.00189 |
Grade A, and why
remogram-consumer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
When a write id is **not** configured, Remogram fails closed with **`write_not_configured`**. When writes **are** configured, `doctor` emits **`curl_bridge_deprecated`** — use Remogram writes, not raw API curl. How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remogram Consumer
Use when the workspace has .remogram.json at the repo root, Remogram CLI on PATH, or Remogram MCP enabled. Remogram supplies forge facts only — not workflow routing from planning tools.
Bootstrap
remogram doctor --json
remogram version --json
remogram provider capabilities --json
remogram repo status --json
remogram plugin boundary --json
remogram evidence forge-facts --cr <number> --json
Use plugin boundary (no .remogram.json required) to discover forge-only emit surfaces and linkage to contract export.
Use evidence forge-facts when consumers need a bounded remogram.forge_facts.v1 producer section for evidence packet composition instead of scraping individual command packets.
Fix doctor failures before trusting other packets. Doctor checks config schema, remote parsing, owner/repo match, trusted host binding, auth env presence (never values), provider capabilities, forge write budget, and operator write overlay bind when present.
Forge write budget (spec-sized bodies)
Before large-body writes, read the budget — do not trial-and-error inline --body:
remogram doctor --json | jq '.forge_write_budget'
remogram write preview --kind issue_open --title "..." --body-file ./spec.md --json
Default inline write cap is 512 bytes. For spec-sized content use --body-file with a bounded env override:
REMOGRAM_WRITE_FIELD_MAX_BYTES=65536 remogram issue open --title "..." --body-file ./spec.md --json
forge_write_budget reports recommended_bounded_override, body_file_by_command, and agent_safe_default. Read packets stay capped at 512 bytes regardless of write override.
Config
Copy from Remogram's .remogram.json.example. Typical shape:
{
"version": "1",
"provider": "gitea-api",
"remote": "origin",
"owner": "org",
"repo": "project",
"baseUrl": "https://forge.example"
}
| Provider | Auth env (first wins) |
|---|---|
gitea-api |
GITEA_TOKEN |
github-api |
GITHUB_TOKEN, then GH_TOKEN |
gitlab-api |
GITLAB_TOKEN |
What ships with it
7 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 · 175 lines · 47 tokens per session scan A ad7f507d0127
remogram-consumer is a skill published in the GitHub repository attebury/remogram (0 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 1,892 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
hatch3r-cli-gh
GitHub CLI — repos, issues, PRs, releases, gists. Use when drafting GitHub pull requests, issues, releases, gists, or workflow dispatches; invoke gh. Authenticates via the platform's native token mechanism (OAuth / PAT).
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
gh-skill
Manage agent skills with gh skill. Use this skill to discover, preview, install, update, and publish Agent Skills so an agent can self-manage the skills available in its environment.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
conventional-commit
Conventional Commit - Generate Conventional Commits 1.0.0 compliant messages. MANDATORY for all git commits. Invoke when user says 'commit', 'commit this', or asks to commit code.