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 juxt/allium --skill propagategit clone --depth 1 https://github.com/juxt/alliumWrote 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/juxt/allium/propagate)<a href="https://agentmods.dev/skills/juxt/allium/propagate"><img src="https://agentmods.dev/badge/skills/juxt/allium/propagate/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/juxt/allium/propagate"><img src="https://agentmods.dev/badge/skills/juxt/allium/propagate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00057 | $0.04443 |
| Opus 5.5 | $0.00023 | $0.01777 |
| Sonnet 5.5 | $0.00011 | $0.00889 |
| Haiku 4.5 | $0.00006 | $0.00444 |
Grade A, and why
propagate 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- propagate — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Propagation
This skill generates tests from Allium specifications. Propagation is how plants reproduce from cuttings of the parent: the spec is the parent, the tests are the offspring.
Deterministic tools guarantee completeness (every spec construct maps to a test obligation). You handle the implementation bridge: correlating spec constructs with code, generating tests in the project's conventions.
Interaction modes
This skill runs in two modes. Every instruction below that asks or suggests something to the user follows the mode:
- Interactive — running inline in a conversation. Ask the user directly and wait for the answer.
- Non-interactive — running as the
propagatesubagent (for example inside the Allium loop), where no user is reachable. Report anything that needs a human decision — a spec too coarse to propagate, an ambiguous implementation bridge, uncovered obligations — in your final output and continue with the work that does not depend on it.
Prerequisites
Before propagating tests, you need:
- An Allium spec — the
.alliumfile describing the system's behaviour - A target codebase — the implementation to test
- Test obligations — from
allium plan <spec>(JSON listing every required test) - Domain model — from
allium model <spec>(JSON describing entity shapes, constraints, state machines)
If the CLI tools are not available, derive test obligations manually from the spec using the test-generation taxonomy in references/test-generation.md.
Modes
Surface mode
Generates boundary tests from surface declarations. Use when the user wants to test an API, UI contract or integration boundary.
For each surface in the spec:
- Exposure tests — verify each item in
exposesis accessible to the specified actor, includingforiteration over collections - Provides tests — verify operations appear when their
whenconditions are true and are hidden otherwise, including when the corresponding rule'srequiresclauses are not met - Actor restriction tests — verify the surface is not accessible to other actor types
- Actor identification tests — verify only entities matching the actor's
identified_bypredicate can interact; for actors withwithin, verify interaction is scoped to the declared context - Context scoping tests — verify the surface instance is absent when no entity matches the
contextpredicate - Contract obligation tests — verify
demandsare satisfied by the counterpart,fulfilsare supplied by this surface, including all typed signatures - Guarantee tests — verify
@guaranteeannotations hold across the boundary - Timeout tests — verify referenced temporal rules fire within the surface's context
- Related navigation tests — verify navigation to related surfaces resolves to the correct context entity
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.
- 1mo ago First seen · 274 lines · 57 tokens per session scan A 5e2d88808bd9
propagate is a skill published in the GitHub repository juxt/allium (513 stars, last pushed 20d ago), licensed MIT. It adds 57 tokens to every session and 4,443 once invoked, about $0.0002 per session on Opus 5.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
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction using playwright-cli. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, extract information from web pages, mock network requests, manage browser…
kiro-validate-impl
Validate feature-level integration after all tasks are implemented. Checks cross-task consistency, full test suite, and overall spec coverage.
gsd-add-tests
Generate tests for a completed phase based on UAT criteria and implementation.
gsd-verify-work
Validate built features through conversational UAT.
gsd-eval-review
Audit an executed AI phase's evaluation coverage and produce an EVAL-REVIEW.md remediation plan.
gsd-validate-phase
Retroactively audit and fill Nyquist validation gaps for a completed phase.