Gini Agent is a personal AI-agent runtime that manages conversations, runs, tasks, approvals, memory, skills, jobs, tools, traces, audit events, and runtime health across its clients. It is for an agent that can remember, learn from task outcomes, and operate through desktop or mobile interfaces with user controls. Catalogue add-ons extend the runtime with skills and instructions.
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 Open-Curiosity/gini-agent --skill gini-bug-reportgit clone --depth 1 https://github.com/Open-Curiosity/gini-agentWrote 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/open-curiosity/gini-agent/gini-bug-report)<a href="https://agentmods.dev/skills/open-curiosity/gini-agent/gini-bug-report"><img src="https://agentmods.dev/badge/skills/open-curiosity/gini-agent/gini-bug-report/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/open-curiosity/gini-agent/gini-bug-report"><img src="https://agentmods.dev/badge/skills/open-curiosity/gini-agent/gini-bug-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.03146 |
| Opus 5 | $0.00023 | $0.01573 |
| Sonnet 5 | $0.00009 | $0.00629 |
| Haiku 4.5 | $0.00005 | $0.00315 |
Grade A, and why
gini-bug-report 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 9d 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gini Bug Report
File a Gini crash that was captured locally — and redacted at capture time —
as a GitHub issue, but only after the user says yes. This skill is the
consent-aware orchestration layer on top of the github-issues skill: it
reads the pending crash queue, summarizes it for the user, and on a "yes"
delegates the actual gh filing to github-issues. It never invents crash
data and never re-reads raw logs.
When To Use
- The crash-report consent flow invoked you: on restart of the
defaultinstance, Gini posted a chat message asking whether to file captured crash(es). The user replied in that thread — act on their answer here. - The user explicitly asks to report a captured crash ("file that crash", "report the crash you found").
When NOT to Use
- General GitHub issue work (create/search/triage/label/close) → use the
github-issuesskill directly; this skill only files queued crashes. - A non-crash bug report, feature request, or any issue not already sitting
in the crash queue → use
github-issuesand write the body yourself. - Anything that would need un-redacted data (raw
runtime.jsonl, secrets, full logs) → out of scope. The queued report is the trust boundary; never go around it. - Proactively scanning the queue or nagging the user → don't. Only act when invoked by the consent flow or an explicit request.
The crash queue
Approved terminal_exec runs with the working directory set to the
workspace root — not this skill's directory and not the crash
directory. Address the queue by ABSOLUTE path. Define it once and reuse it:
QUEUE="${GINI_STATE_ROOT:-$HOME/.gini}/crash-reports"
Layout:
$QUEUE/pending/*.json— captured crashes awaiting a consent decision.$QUEUE/filed/— reports the user agreed to file (moved here after a successfulghfiling).$QUEUE/dismissed/— reports the user declined.
Each pending file is one JSON crash report with this shape (field names are exact):
{ instance, source, supervisor, fingerprint, at,
error: { name, message, stack },
sysInfo: { platform, arch, nodeVersion, giniCommit },
logTail: [ { at, message }, ... ] }
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.
- 9d ago First seen · 287 lines · 47 tokens per session scan A 1d1b31b90d6b
gini-bug-report is a skill published in the GitHub repository Open-Curiosity/gini-agent (2,018 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 3,146 once invoked, about $0.0002 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-30.
Other skills, from other repositories
smiles-validation
Strict SMILES validation, structural comparison, and modification verification. Catches invalid LLM-generated molecules.
review
Review code changes, pull requests, patches, or a scoped code area for actionable correctness, security, compatibility, and test risks with file and line evidence. Use for review or audit requests; do not use for general proofreading, feature implementation, or debugging a reported failure when the user wants a fix.
debug
Diagnose a concrete failure, regression, crash, hang, flaky test, or incorrect runtime behavior by reproducing it, testing hypotheses, and identifying the evidence-backed root cause. Use when symptoms or failing output exist; do not use for feature implementation without a failure, general code review, or a conceptual…
simplify
Reduce unnecessary code complexity, duplication, indirection, or abstraction while preserving observable behavior and validating equivalence. Use for simplify, cleanup, or behavior-preserving refactor requests; do not use for adding features, diagnosing an unexplained failure, broad code review without a…
autogpt-agents
Autonomous AI agent platform for building and deploying continuous agents. Use when creating visual workflow agents, deploying persistent autonomous agents, or building complex multi-step AI automation systems.
loop-triage
Triage recent changes, CI failures, issues, and conversations. Produces a concise, actionable findings report suitable for a loop to consume. Writes structured output to a state file or Linear board.