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/peintune/runjam/runjam-defaultsnpx skills add peintune/runjam --skill runjam-defaultsgit clone --depth 1 https://github.com/peintune/runjamWrote 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/peintune/runjam/runjam-defaults)<a href="https://agentmods.dev/skills/peintune/runjam/runjam-defaults"><img src="https://agentmods.dev/badge/skills/peintune/runjam/runjam-defaults.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.00059 | $0.02696 |
| Opus 5 | $0.00030 | $0.01348 |
| Sonnet 5 | $0.00012 | $0.00539 |
| Haiku 4.5 | $0.00006 | $0.00270 |
Grade A, and why
runjam-defaults scanned grade A 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 4d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- **Shell quoting:** When passing values with `$`, `!!`, `#`, spaces, or special characters into a shell command, **single-quote** the value to prevent expansion. In Python `subprocess.run([...])` list form, quoting is n How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RunJam Default Constraints
These are non-negotiable defaults that apply to every session. They prevent common Agent mistakes: outputting files to wrong directories, using unavailable dependencies without a fallback, and making assumptions about the environment.
Treat every rule below as a HARD RULE — violating any one means the task is not done, regardless of content quality.
0. Path Convention (READ FIRST — prevents the #1 Agent mistake)
Every relative path in this document and in every skill's SKILL.md is relative to the SESSION WORKING DIRECTORY — NOT the skill's own directory.
| Term | Meaning |
|---|---|
| Session working directory | The directory where the Agent process runs. This is the session root — e.g. ~/.runjam/session/<id>/ or the user-selected project folder. All ./ paths resolve here. |
| Skill directory | Where the SKILL.md lives — e.g. .claude/skills/ppt-generation/. NEVER create outputs/ or workspace/ inside a skill directory. The skill directory is read-only resources. |
This session's working directory (absolute path)
/Users/guizhan/work/code/runjam
The Agent process was started with this directory as its cwd. Every relative path below resolves relative to it. If pwd disagrees with the absolute path above, trust the absolute path above and cd to it first — it is the authoritative session root for this session.
The rule
When a SKILL.md says ./outputs/ or ./workspace/, it means:
<session working directory>/outputs/ ← deliverables go HERE
<session working directory>/workspace/ ← helper scripts go HERE
NOT:
<session working directory>/.claude/skills/<skill-name>/outputs/ ← WRONG
<session working directory>/.claude/skills/<skill-name>/workspace/ ← WRONG
Path safety check (MANDATORY in every generated script)
At the top of any Python script you generate, include this guard to ensure outputs land in the session root, not inside a skill folder:
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.
- 4d ago First seen · 207 lines · 0 tokens per session scan A 00cb414fc028
runjam-defaults is a skill published in the GitHub repository peintune/runjam (128 stars, last pushed 4d ago), licensed MIT. It adds 59 tokens to every session and 2,696 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
map-review
Interactive 4-section code review using monitor, predictor, and evaluator agents plus the user and maintainer role reviewers on current changes. Use when reviewing a diff, PR, or staged work before merge. Do NOT use to plan or implement; use map-plan or map-efficient.
map-debug
Structured MAP debugging via task-decomposer, actor, and monitor agents. Use when reproducing a bug, isolating a regression, or diagnosing an error with specialized agents — including failing or flaky tests (pytest AssertionError), crashes and segmentation faults, memory-corruption or memory errors in native/C…
map-learn
Capture reusable lessons after a completed MAP workflow. Use when a MAP run has finished and you want rules written to .claude/rules/learned/ from a workflow summary or handoff. Do NOT use during active implementation.
map-explain
Deep walkthrough of code, a diff, or the whole project — problem, entities, flow, load-bearing-line rationale, side effects, assumptions, breakage. Use when learning unfamiliar code or auditing a diff.
map-task
Execute a single subtask from an existing MAP plan via Actor and Monitor. Use when map-plan has decomposed work and you want fine-grained control over one subtask. Do NOT use without an existing plan; run map-plan first.
ubiquitous-language
Maintain a project thesaurus (domain glossary) following DDD ubiquitous language principles. Use PROACTIVELY when naming anything: variables, functions, classes, modules, database fields, API endpoints, events, files, or directories. Also use when the user asks to "create thesaurus", "update glossary", "add term"…