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/dylanroscover/embody/parameter-designnpx skills add dylanroscover/Embody --skill parameter-designgit clone --depth 1 https://github.com/dylanroscover/EmbodyWrote 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/dylanroscover/embody/parameter-design)<a href="https://agentmods.dev/skills/dylanroscover/embody/parameter-design"><img src="https://agentmods.dev/badge/skills/dylanroscover/embody/parameter-design.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.00032 | $0.04700 |
| Opus 5 | $0.00016 | $0.02350 |
| Sonnet 5 | $0.00006 | $0.00940 |
| Haiku 4.5 | $0.00003 | $0.00470 |
Grade A, and why
parameter-design 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Always write through `store()`, never `comp.storage[k] = v`.** Re-storing an unchanged value still notifies, so `store(k, fetch(k))` is the documented way to publish an in-place mutation. How it starts
The opening of the file, as written. The whole thing — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parameter Design
Ownership and Lifecycle
Code owns the schema; the user owns the value. A parameter's name, style, page, range, default and help text are yours to declare and re-assert. Its value is the user's, and nothing you write may quietly discard it.
Extensions reinitialize on every source-file save, so every creation path must be get-or-create, never create-blindly:
def ensureCustomPage(comp, name):
for page in comp.customPages:
if page.name == name:
return page
return comp.appendCustomPage(name)
def ensureCustomPar(comp, page, name, style, **attrs):
"""Get-or-create one custom par: the Par, or the ParGroup for a tuplet."""
# Probe the WHOLE COMP by tupletName. Names are a flat per-COMP namespace,
# and a multi-value style (RGB, XYZ) is stored as <name>r/<name>g/<name>b,
# so a probe by .name never finds it and append*() (replace=True) would
# re-create it on every reinit.
found = [p for p in comp.customPars if p.tupletName == name]
if not found:
getattr(page, 'append' + style)(name)
found = [p for p in comp.customPars if p.tupletName == name]
elif found[0].style not in STYLE_FAMILY.get(style, (style,)):
raise ValueError('par %s is %s, declared %s -- refusing to replace it'
% (name, found[0].style, style))
for p in found: # symmetric: schema attrs re-applied
for key, value in attrs.items(): # on every reinit; the user's state
if key not in ('val', 'expr', 'bindExpr', 'mode', 'export'):
setattr(p, key, value) # is never touched -- and a typo RAISES
return found[0] if len(found) == 1 else found[0].parGroup
# TD reports a tuplet's style by family: RGB reads 'RGBA', XY/XYZ read 'XYZW'.
STYLE_FAMILY = {'RGB': ('RGB', 'RGBA'), 'XY': ('XY', 'XYZW'), 'XYZ': ('XYZ', 'XYZW')}
Four rules that make it safe:
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.
- today Changed · +18 lines 5ba416e7d7b7
- 5d ago First seen · 291 lines · 32 tokens per session scan A 33ffe0c34fc0
parameter-design is a skill published in the GitHub repository dylanroscover/Embody (169 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 4,700 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
test-quality
Test quality bar for this repo. Read when writing, reviewing, or designing tests — covers naming, abstraction level, assertions, determinism, and the process for agent-driven test work.
touchdesigner-self-debug
A generic workflow for self-starting TouchDesigner via computer-use (or an already-running instance), loading mcpwebserverbase.tox, and verifying any TD-side Python change (td/modules/) directly from the Textport — reading back real TD runtime values and reconciling them. Use after changing TD-side code in the…
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.
amazon aurora dsql
Deprecated compatibility redirect for Aurora DSQL guidance. Use when a request concerns DSQL, Aurora DSQL, distributed SQL, DSQL schemas, migrations, queries, authentication, performance, or application development.
resolve-pr-comments-stack
Resolve unresolved PR review comments across an entire Graphite (gt) stack of many PRs, bottom-up, in one working directory. Use when asked to "go through this stack and resolve comments", "clean up review comments across the whole stack", or given a list/range of PR numbers that form (or partially form) a gt stack.…
split-commit-into-stack
Split one oversized commit or branch into a stack of independently reviewable Graphite (gt) PRs - deciding what genuinely separates, what is atomic and must stay whole, and proving each lower PR builds and passes without the ones above it. Use when asked to "split this PR", "this commit is too big", "break this into a…