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 Ramsbaby/jarvis --skill goalgit clone --depth 1 https://github.com/Ramsbaby/jarvisWrote 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/ramsbaby/jarvis/goal)<a href="https://agentmods.dev/skills/ramsbaby/jarvis/goal"><img src="https://agentmods.dev/badge/skills/ramsbaby/jarvis/goal/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/ramsbaby/jarvis/goal"><img src="https://agentmods.dev/badge/skills/ramsbaby/jarvis/goal.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.00067 | $0.00662 |
| Opus 5 | $0.00034 | $0.00331 |
| Sonnet 5 | $0.00013 | $0.00132 |
| Haiku 4.5 | $0.00007 | $0.00066 |
Grade C, and why
jarvis-goal scanned grade C 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- `rm -rf`, `DROP TABLE`, `TRUNCATE` How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/goal — Goal-Driven Autonomous Execution
Set a measurable completion condition once; the agent self-verifies every turn until the condition is met, then declares done with evidence.
How it works (4 stages)
- Parse completion condition → normalize to a verifiable predicate
- Per-turn self-check → after each action, ask "is the condition met?" using actual tool output, not assumption
- Auto-continuation → if not met, continue without waiting for Stop hook
- Stop on success → declare completion citing real command output as evidence
Example inputs:
/goal all crons sustained ≥ 95% success over 7 days/goal /verify 7-gate all PASS/goal rag indexing complete + integrity check passes
⚠️ Irreversibility Guard (auto-pause triggers)
Autonomous execution pauses and requests explicit user approval when detecting:
git push,git push --force- Repo visibility changes, deletion, archival (
gh repo edit --visibility,gh repo delete,gh repo archive) - External message dispatch (Slack, email, Discord public channels, push notifications)
- Payment, financial transfer, asset movement, trade execution
- Secret or PII exposure to external systems
- Irreversible system changes (production DB schema, mass data deletion, cron mass disable)
rm -rf,DROP TABLE,TRUNCATE
Pause format:
"Irreversible operation detected: [name]. Scope: [blast radius]. Approve to proceed?"
Differentiation vs. Anthropic /goal
- Built-in irreversibility guard with explicit pause behavior (the official command has no such guard)
- Optional ledger integration for token accounting per goal
- Composable with
/verifyand/doctorfor complex condition predicates
Self-check (before declaring completion — BLOCKING)
- Did I confirm the evidence via actual tool output, not assumption?
- Have I triggered any irreversibility guard pattern unintentionally?
- Did I avoid declaring completion based on partial metrics (e.g., only load average without memory/disk)?
- Have I considered at least three alternative hypotheses for any failure I diagnosed?
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 · 63 lines · 67 tokens per session scan C 4072e649a964
jarvis-goal is a skill published in the GitHub repository Ramsbaby/jarvis (16 stars, last pushed 17d ago), licensed MIT. It adds 67 tokens to every session and 662 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
cognition-authority
How to hold the controls of the Cognition Discord server — you are the first actor there, not an assistant waiting for instructions. Read this before any other Cognition skill and before the first action of any session touching guild 1535979812860993617. It settles who decides, how to read a request as intent rather…
build-system
A skill for building interactive systems in the Cognition Discord server by combining Registry building blocks instead of writing code. These systems can include tickets, applications, voting, verification, and menus for choosing roles.
registry-authoring
A reference for the Cognition Registry, including its action types, parameters, conditions, template variables, and known configuration mistakes.
danger
A safety protocol for irreversible operations on a Cognition server, such as deleting a channel, category, or role. It requires taking a snapshot, previewing the change, getting human approval, and then applying it.
react-to-events
A skill for making a Cognition Discord server respond automatically to events such as members joining, keywords being posted, reactions, or channels being deleted.
run-session
A procedure for running experiments on a Cognition Discord server from a temporary test stage to a permanent or archived result.