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 commands/onehillai/asdd/setupgit clone --depth 1 https://github.com/OneHillAI/ASDDWhat 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.00011 | $0.00259 |
| Opus 5 | $0.00005 | $0.00130 |
| Sonnet 5 | $0.00002 | $0.00052 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
setup 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 yesterday.
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
Set up ASDD's agents for this repo.
Run asdd setup and walk the maintainer through it in plain language. It reads the roles from
.asdd.yml, writes the chosen model names back, and asks which spec tool validates readiness -
builtin (ASDD's definition of ready) or openspec (delegate to openspec validate). If they pick
OpenSpec, remind them to install it where the gate runs (npm install -g @fission-ai/openspec).
Hold these rules; do not let a convenient answer break them:
- Model NAMES go in
.asdd.yml. A key never does: that file is version-controlled. Credentials belong in Goose's own config (goose configure) or a CI secret (ASDD_RUNTIME_TOKEN). developeris bring-your-own: the contributor's own agent, not something the deployment runs.- The test models MUST differ from the developer's, or their blind spots line up and the tests
cheerfully confirm the bug.
asdd check-models --strictenforces it.
Finish by showing what is set and what is still unset.
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.
- yesterday First seen · 19 lines · 11 tokens per session scan A db8df3ecf8ad
setup is a command published in the GitHub repository OneHillAI/ASDD (5 stars, last pushed 20d ago), licensed Apache-2.0. It adds 11 tokens to every session and 259 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-31.
Other commands, from other repositories
MIGRATE_DESIGN
Design doc for the migration tool PR. Author: Sol ([email protected]). Co-authored-by: wakesync.
install-context
Install OpenAgents Control context files.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
plan
Create a structured task-by-task implementation plan for a feature and write it to docs/superpowers/plans/.
diff-script
Compare an MDL script against the project's current state.
toh-help
Display all Toh Framework commands and quick usage guide.