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/l1vein/rambledesk/ramblenpx skills add l1veIn/rambledesk --skill ramblegit clone --depth 1 https://github.com/l1veIn/rambledeskWrote 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/l1vein/rambledesk/ramble)<a href="https://agentmods.dev/skills/l1vein/rambledesk/ramble"><img src="https://agentmods.dev/badge/skills/l1vein/rambledesk/ramble.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.1 | $0.00081 | $0.01379 |
| Opus 5 | $0.00041 | $0.00690 |
| Sonnet 5 | $0.00016 | $0.00276 |
| Haiku 4.5 | $0.00008 | $0.00138 |
Grade A, and why
ramble 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 6d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ramble — run a human-feedback loop through RambleDesk
Route anything that needs a real human's judgment, review, approval, or hands-on experience through the RambleDesk feedback loop instead of asking in chat.
Invocation contract
- Treat explicit invocation as a command, not a hint. If the user invokes
/ramble,$ramble,[$ramble], names this skill as the way to handle the task, or asks for RambleDesk feedback, create the first RambleDesk request before substantive advice, design, review, or implementation. - Treat
/ramble [task]as a task-scoped loop. Guarantee the first request, then create later serialized requests only when the same task needs another clarification, review, or final confirmation. Do not carry the loop into an unrelated future task. - Treat an empty argument or a generic starter such as "start this Ramble" or
"Let's work on something together" as no meaningful task:
- If the conversation already contains one clear active task, summarize the current understanding in the kickoff request and ask the human to confirm or correct it while supplying any missing context, constraints, desired output, priorities, and completion criteria.
- Otherwise create a kickoff request asking the human for the goal, relevant context and materials, constraints, desired output, priorities, and completion criteria.
- Ask for this task brief in RambleDesk, never in the host chat.
- Treat
/ramble_onand/ramble_off, when the host provides them, as persistent-mode switches rather than one-task skill invocations. - Use this skill implicitly when human testing, visual inspection, screenshots, clarification, or a decision would materially improve the result.
- Do not treat a meta request to inspect, edit, or debug this skill as a request to create feedback unless the user also explicitly asks to run the loop.
Select the available flow
Prefer the native adapter flow when a tool equivalent to
request_ramble_feedback is available. Otherwise use the Generic MCP flow with
a tool equivalent to request_feedback. Discover renamed RambleDesk tools by
capability before deciding that no request tool exists.
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.
- 6d ago First seen · 118 lines · 81 tokens per session scan A 9e9b56062cb6
ramble is a skill published in the GitHub repository l1veIn/rambledesk (20 stars, last pushed yesterday), licensed MIT. It adds 81 tokens to every session and 1,379 once invoked, about $0.0004 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
product-update-newsletter
Draft, update, or audit a crisp, changelog-grounded Anarlog product-update newsletter in Loops (app.loops.so) for a desktop release. Use after the changelog is merged, when asked to draft, revise, or pre-send check the release announcement email.
qa-cli-mcp-api
Select and run explicitly requested, risk-based QA for Anarlog's CLI, webhooks, stdio MCP, hosted Cloud API, and remote MCP. Test only affected lanes unless comprehensive coverage is requested.
release-new-version
Release a new desktop stable version for Anarlog. Use when asked to cut, publish, or prepare a new stable desktop release after checking and merging the changelog.
sqlite-schema-design
Design or review schemas for crates/cloudsync using SQLite Sync constraints, not generic SQLite advice. Use when adding synced tables, changing synced columns, or planning CloudSync-safe migrations.
fix-ready-prs
Inspect every open non-draft PR for CI failures and unresolved Cursor Bugbot findings, then fix them on the existing PR branches. Use when asked to check active PRs, triage ready PRs, fix CI, or address Bugbot comments.
reactive-sqlite-ui
Build SQLite-backed reactive UI in apps/desktop using stable patterns for reads, selection, forms, writes, and loading states. Use when implementing or reviewing screens built on useDrizzleLiveQuery and SQLite mutations.