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/rivet-dev/agentos/gigacode-api-sanitynpx skills add rivet-dev/agentos --skill gigacode-api-sanitygit clone --depth 1 https://github.com/rivet-dev/agentosWhat 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.00067 | $0.00960 |
| Opus 5 | $0.00034 | $0.00480 |
| Sonnet 5 | $0.00013 | $0.00192 |
| Haiku 4.5 | $0.00007 | $0.00096 |
Grade A, and why
gigacode-api-sanity 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 3d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GigaCode API Sanity
Run a black-box parity check. Do not modify product source or disturb an existing daemon.
Set up
- Run
pwdandjj log -r @; record the revision and both runtime versions. - Create one fresh temp root containing separate native and GigaCode workspaces, logs, and raw traces.
- Pick unused API/Rivet ports. Never reuse or stop the default ports
2468/2469. - Start native
opencode servein its workspace. Start GigaCode in its workspace with unique state and port environment variables. Prefer the current checkout; disclose any installed-runtime fallback. - Open
/eventbefore creating a session and preserve the unmodified SSE stream. - Check
/global/healthand/provider. Require a working Claude Sonnet credential on both sides before judging model behavior. For GigaCode, pin Sonnet withGIGACODE_SESSION_ENV_JSON, for example{"ANTHROPIC_MODEL":"claude-sonnet-4-6"}.
Treat authentication failure as a setup limitation, not an API deviation. Do not claim full parity without a valid native Sonnet run.
Run the same scenario on each server
Use direct HTTP requests and save status, headers, body, timing, and SSE frames for every step:
POST /session; record the complete response.- Send two synchronous
POST /session/{id}/messageprompts in the same session. Make turn two depend on turn one. - Prompt the agent to create
api-edit.txtwith exact contents using a tool. PollGET /permission, reply once throughPOST /permission/{id}/reply, and verify both the tool-part lifecycle and host file contents. - Start a long tool call with
POST /session/{id}/prompt_async. Use a command such astouch <workspace>/sleep-started && sleep 20, poll permissions concurrently, and approve the tool if required. Wait for either the marker file or the tool part to berunningbefore callingPOST /session/{id}/abort. The marker proves the command actually began even when an implementation publishes tool events late. Merely observing the session as busy can mean the model is still deciding what tool to call and does not validate tool-process cancellation. - Immediately send another synchronous prompt on that same session. Poll and resolve permissions concurrently while that request is in flight: an aborted tool instruction remains in model history and some models repeat it on the next turn. The follow-up must finish and return to idle.
- Fetch final messages, parts, permissions, and
/session/status.
What ships with it
1 file 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.
- 3d ago First seen · 53 lines · 67 tokens per session scan A 8c892f044c81
gigacode-api-sanity is a skill published in the GitHub repository rivet-dev/agentos (4,444 stars, last pushed 2d ago), licensed Apache-2.0. It adds 67 tokens to every session and 960 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-30.
Other skills, from other repositories
maintain-model-list
Maintain the supported LLM model list: add a new model, or run routine maintenance to verify availability and discover new models worth adding. Use when the user asks to add/support a model, update the model list, or check model availability.
update-changelog
Update docs/CHANGELOG.md from git history, GitHub releases, and code diffs. Use when: writing release notes, syncing the latest changelog entry, summarizing a new tag, or keeping changelog wording concise and consistent.
git-cleanup
Clean up local git branches and remotes accumulated from PR reviews. Use when the user asks to clean branches, remove stale remotes, or tidy up the local git state.
submit-pr-from-current-changes
Create a branch, commit existing local changes, push them, and open a pull request. Use when submitting current work as a PR.
pre-impl-discussion
Conduct a thorough pre-implementation discussion before making significant changes. Use when the user wants to discuss, plan, or evaluate a change before implementing it — especially when they say words like 'discuss', 'evaluate', 'plan', or 'let's talk about'.
gh-pr-description
Drafts and reviews GitHub pull request descriptions for the eve repository. Use when opening, updating, or reviewing a PR, or when summarizing a branch for reviewers.