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/understudy-ai/understudy/render-brief-assetsnpx skills add understudy-ai/understudy --skill render-brief-assetsgit clone --depth 1 https://github.com/understudy-ai/understudyWhat 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.00018 | $0.00186 |
| Opus 5 | $0.00009 | $0.00093 |
| Sonnet 5 | $0.00004 | $0.00037 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
render-brief-assets 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 2d 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.
What it actually says
render-brief-assets
Overall Goal
Render the final visual assets for the brief package from the target context and summary.
Inputs
- target.json
- summary.json
- brief.md
- highlights.json
Outputs
- cover.png
- summary-card.png
Staged Workflow
- Read the target metadata and summary.
- Render the cover with the target title and verdict.
- Render the summary-card image with ratings and highlights.
Tool Route Options
- shell plus ffmpeg for deterministic rendering
Detailed GUI Replay Hints
- None. This stage should not depend on GUI state.
Failure Policy
- If one asset fails, keep the successful asset and surface a recovery note.
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.
- 2d ago First seen · 44 lines · 18 tokens per session scan A 57db751be8a0
render-brief-assets is a skill published in the GitHub repository understudy-ai/understudy (456 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 186 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 skills, from other repositories
release-openclaw-maintainer
Prepare or verify OpenClaw stable, beta, and extended-stable releases, including backport discovery, changelogs, release notes, publish commands, and artifacts.
openclaw-testing
Choose, run, rerun, or debug OpenClaw tests, CI checks, Docker E2E lanes, release validation, and the cheapest safe verification path.
autoreview
Structured Codex, Claude, Amp, Pi, or Kimi code review when explicitly requested.
release-openclaw-ci
Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.
auto-qa
Continuously audit, live-test, and stress-test the current OpenClaw codebase across at least ten independently scoped subsystem lanes; default to 100 independently verified, landed root-cause fixes, maintain an evidence-backed report, and announce each merged pull request immediately. Use for OpenClaw-wide autonomous…
openclaw-changelog-update
Regenerate OpenClaw release changelog sections from git history before beta, stable, or extended-stable releases.