lineage: Skill for Claude Code

.agents/skills/lineage-package-security-guardrails/SKILL.md

lineage-package-security-guardrails is a skill for Claude Code, Codex from agentic-lineage/lineage. It costs 57 tokens per session (447 once invoked), scanned A, original, MIT.

A set of security rules for Lineage packages, which are portable local environments that can be inspected and activated on another machine.

In plain words
What is it for?
Use it when validating, exporting, importing, materializing, or activating packages and their files.
Why use it?
It helps prevent packages from carrying secrets, escaping their intended workspace, or running hidden setup actions during import or activation.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is agentic-lineage/lineage's own configuration. It tells Claude Code and Codex how to work on lineage itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything lineage configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/agentic-lineage/lineage/main/.agents/skills/lineage-package-security-guardrails/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/agentic-lineage/lineage

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for lineage-package-security-guardrails

README.md
[![agentmods](https://agentmods.dev/badge/skills/agentic-lineage/lineage/lineage-package-security-guardrails/github.svg)](https://agentmods.dev/skills/agentic-lineage/lineage/lineage-package-security-guardrails)
Your own site
<a href="https://agentmods.dev/skills/agentic-lineage/lineage/lineage-package-security-guardrails"><img src="https://agentmods.dev/badge/skills/agentic-lineage/lineage/lineage-package-security-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.

agentmods 80×15 button for lineage-package-security-guardrails

Your own site · 80×15
<a href="https://agentmods.dev/skills/agentic-lineage/lineage/lineage-package-security-guardrails"><img src="https://agentmods.dev/badge/skills/agentic-lineage/lineage/lineage-package-security-guardrails.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 447 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00057 $0.00447
Opus 5.5 $0.00023 $0.00179
Sonnet 5.5 $0.00011 $0.00089
Haiku 4.5 $0.00006 $0.00045

Measured 1mo ago against content hash 00f12296a9d0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

lineage-package-security-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 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.

.agents/skills/lineage-package-security-guardrails/SKILL.md · 44 lines

How it starts

The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Lineage Package Security Guardrails

Lineage packages are portable local environments. A receiver should be able to inspect what a package will do before it changes their workspace.

Threat Model

Assume every package is untrusted until validated. A malicious or careless package may try to:

  • include secrets or private local state;
  • reference files outside the package;
  • write outside the intended workspace;
  • smuggle symlinks or path traversal entries;
  • hide risky setup actions behind normal activation;
  • make provider-specific assumptions look like core behavior.

Safety Rules

  • Import and inspect must not execute setup actions.
  • Setup and materialization must be explicit, reviewable, permission-gated, and idempotent.
  • Never package API keys, auth tokens, .env values, credential stores, provider login state, shell history, or machine-local caches.
  • Secret checks may report file paths and reasons, but not matched values.
  • Prefer templates, schemas, sample CSVs, and placeholder config when private source data should not travel.
  • Validate every package-controlled path before reading or writing. Absolute paths and .. traversal are unsafe unless a specific user-provided destination explicitly allows them.
  • Reject or deliberately handle symlinks. Do not silently follow package symlinks into the receiver's machine.
  • Keep capability declarations honest and human-readable. Do not imply enforcement exists until code actually enforces it.

Review Questions

  • What exactly can the receiver inspect before enabling or running this package?
  • What files will be created, modified, or deleted?
  • Can the operation be declined without partial side effects?
  • Can the same operation run twice without drift?
  • Are source-user data and receiver-local config clearly separated?
  • Is provider-specific behavior isolated behind an adapter?

Required Verification

Add tests for unsafe paths, secret-shaped inputs, repeated setup/materialization, and declined permission flows when those surfaces change.

Read the full file on GitHub · 44 lines

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.

  1. 1mo ago First seen · 44 lines · 57 tokens per session scan A 00f12296a9d0

Subscribe to this mod's changes

lineage-package-security-guardrails is a skill published in the GitHub repository agentic-lineage/lineage (11 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 447 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-31.