Borrowing it
Nothing to install: this file belongs to agentic-lineage/lineage. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agentic-lineage/lineage/main/.agents/skills/lineage-cli-ux-guardrails/SKILL.mdgit clone --depth 1 https://github.com/agentic-lineage/lineageWrote 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/agentic-lineage/lineage/lineage-cli-ux-guardrails)<a href="https://agentmods.dev/skills/agentic-lineage/lineage/lineage-cli-ux-guardrails"><img src="https://agentmods.dev/badge/skills/agentic-lineage/lineage/lineage-cli-ux-guardrails/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/agentic-lineage/lineage/lineage-cli-ux-guardrails"><img src="https://agentmods.dev/badge/skills/agentic-lineage/lineage/lineage-cli-ux-guardrails.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00054 | $0.00347 |
| Opus 5 | $0.00027 | $0.00173 |
| Sonnet 5 | $0.00011 | $0.00069 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
lineage-cli-ux-guardrails 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 12d 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
Lineage CLI UX Guardrails
Lineage should make agent-environment distribution feel safe for non-expert users without hiding what will happen.
CLI Contract
- Prefer explicit verbs:
package init,package validate,enable,run,install-shims. - Preserve existing command signatures unless the linked issue explicitly calls for a breaking change.
--dry-runmust be side-effect-free.- Interactive prompts must have a non-interactive path for scripts and CI.
- Declining a permission prompt must stop the unsafe operation cleanly.
- Print human-readable summaries by default; keep output deterministic and stable enough to test.
- Send normal command results to stdout and actionable errors to stderr.
Receiver Experience
- Inspect before enable.
- Show what package, digest, capabilities, provider, files, and setup actions are involved.
- Do not ask users to manually assemble plugin/config/tracker files when Lineage can safely prepare templates for them.
- Do not make activation depend on secrets being bundled. Receiver-local secrets and provider login remain local.
- Avoid jargon in user-facing messages. Explain the action, target path, and consequence.
Testing Expectations
- Test help/usage for new commands.
- Test successful output and failure output.
- Test
--dry-run, declined prompts, approved prompts, and repeated runs when the command writes files. - Test provider argument passthrough when launch behavior changes.
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.
- 12d ago First seen · 34 lines · 54 tokens per session scan A 132898851ef6
lineage-cli-ux-guardrails is a skill published in the GitHub repository agentic-lineage/lineage (10 stars, last pushed 3d ago), licensed MIT. It adds 54 tokens to every session and 347 once invoked, about $0.0003 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 skills, from other repositories
fireworks-tech-graph
Create technical diagrams such as software architecture, data flow, flowcharts, sequence diagrams, C4 reviews, cloud deployments, event streams, observability investigations, agent/memory systems, UML, ER, network topology, timelines, and technical concept maps, then export SVG, PNG, focused semantic SVG-to-GIF…
spawn-reviewers
Spawn and collect the reviewer fleet at stage20spawnreviewers. Consumes spawn.json.spec (the authoritative spawn spec from derive-spawn-spec / derive-static-spec), resolves CODEINTELALLOWED, builds per-agent prompts from the per-agent template + role suffixes (Bug Hunter A/B, Unified Auditor, Domain Critics, Impact…
design-inventory
Use to run the Claude Design to ClosedLoop pipeline against the current web-ui. Stage A inventories a design export zip into schema-validated findings (typed design units - screens, regions like nav bars, standalone components like a chat dialog; UX and behavioral changes; Storybook component reuse mapping; token…
artifact-type-tailored-context
Compresses artifacts for judge evaluation. Reads a single raw artifact, applies tiered summarization within a token budget, and returns compacted content with metadata. Isolation via forked context prevents pollution of agent context.
learning-quality
Structured format for capturing high-quality learnings during ClosedLoop runs.
plan-validate
Deterministic plan.json validation via Python script, replacing most plan-validator agent calls. Performs JSON parsing, schema validation, task checkbox regex, required section checks, sync validation, and data extraction. Only semantic consistency checks (storage/query alignment) require the LLM agent. Triggers on…