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 agents/devswat-resonantgenesis/rg_ide/demonstrategit clone --depth 1 https://github.com/DevSwat-ResonantGenesis/RG_IDEWrote 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/agents/devswat-resonantgenesis/rg_ide/demonstrate)<a href="https://agentmods.dev/agents/devswat-resonantgenesis/rg_ide/demonstrate"><img src="https://agentmods.dev/badge/agents/devswat-resonantgenesis/rg_ide/demonstrate.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.00010 | $0.01294 |
| Opus 5 | $0.00005 | $0.00647 |
| Sonnet 5 | $0.00002 | $0.00259 |
| Haiku 4.5 | $0.00001 | $0.00129 |
Grade A, and why
Demonstrate 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 131 lines · 10 tokens per session scan A 1b4254f87219
Demonstrate is an agent published in the GitHub repository DevSwat-ResonantGenesis/RG_IDE (11 stars, last pushed 2mo ago), with no licence file. It adds 10 tokens to every session and 1,294 once invoked, about $0.0001 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 agents, from other repositories
qa
QA specialist that deeply analyzes code produced by the coder agent. Runs the verification skill, traces code paths, checks logic for gaps, unintended changes, edge cases, and omissions. Use proactively after implementation is complete, when coder says "done", or when asked to review/verify code quality.
planner
Planning specialist that creates structured implementation plans for Jira issues. Use proactively when starting a new task, beginning work on a Jira issue, or when asked to plan a feature. Creates the plan and hands over to the implementation agent.
coder
Implementation specialist that writes production code using TDD and commits changes. Use proactively when implementing features, fixing bugs, or writing code for a confirmed plan. Delegates to planner when requirements are unclear or need updating. Hands over to qa when implementation is complete.
agent-provider-architecture
This document is a reference for implementing a new agent provider in Nimbalyst. It is the architectural counterpart to docs/AIPROVIDERTYPES.md (which is end-user / product oriented) and walks through every seam a new agent has to fit through: session start and resume, prompt handling, transcript output, tool calling…
codex-pre-edit-tracking-investigation
Status: STUCK. Three approaches tried, none reliably solves the pre-edit race for update-kind filechange items. This doc captures everything learned so the next session can pick up cleanly without re-deriving.
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.