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-open-source-review-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-open-source-review-guardrails)<a href="https://agentmods.dev/skills/agentic-lineage/lineage/lineage-open-source-review-guardrails"><img src="https://agentmods.dev/badge/skills/agentic-lineage/lineage/lineage-open-source-review-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-open-source-review-guardrails"><img src="https://agentmods.dev/badge/skills/agentic-lineage/lineage/lineage-open-source-review-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.00059 | $0.00399 |
| Opus 5.5 | $0.00024 | $0.00160 |
| Sonnet 5.5 | $0.00012 | $0.00080 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
lineage-open-source-review-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.
What it actually says
Lineage Open Source Review Guardrails
Lineage should be easy to contribute to without letting quality, safety, or roadmap clarity drift.
Contribution Rules
- Contributors should assign an issue before starting work.
- PRs should target
developand link the assigned issue, except maintainer-only housekeeping. - Every PR should include relevant tests added/updated, or a clear no-test reason.
- Keep project-board status simple:
Todo,In Progress,Under Review,Done. - Milestones are goals, not dates.
- Keep labels small and meaningful:
bug,enhancement,documentation,security,critical,needs:decision.
Review Standard
Review for correctness first, then safety, tests, maintainability, and documentation.
Look especially for:
- package inputs treated as trusted;
- provider-specific behavior leaking into core;
- missing tests for safety or idempotency;
- CLI output that cannot be inspected or tested;
- docs that imply future capabilities are already implemented;
- accidental disclosure of private roadmap, secrets, credentials, or machine-local state.
Public Voice
- Keep public docs focused on the agent-environment distribution layer.
- Avoid overpromising marketplace, enterprise, billing, cloud, vector DB, or workflow-engine capabilities.
- Prefer plain explanations of what currently works, what is experimental, and what is intentionally out of scope.
Maintainer Checklist
Before merge:
- Linked issue is assigned or the PR is explicit maintainer housekeeping.
- Required checks pass.
- Tests match the risk of the change.
- Branch target is
develop. - Safety checklist is credible, not just checked.
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 · 47 lines · 59 tokens per session scan A a93fe91e2b81
lineage-open-source-review-guardrails is a skill published in the GitHub repository agentic-lineage/lineage (11 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 399 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.
Other skills, from other repositories
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
ai-agents-generation-and-release
Operate the ai-agents generation and release machinery, covering the seven buildall.py generators, generateagents.py, the drift gates, the version-free plugin manifests, and the npm publish path. Use when you say regenerate the mirrors, run the drift checks, why is the plugin version gate red, release the npm cli. Do…
seal
Ships a feature — simplify pass, certify, commit, PR, CI monitoring, review loop, merge. Use when a feature branch is verified and ready to ship.
raise-pr
Push the current feature branch and raise a GitHub pull request with a conventional-commit style title and a structured body, after verifying the branch actually has committed work to raise. Use this skill whenever the user asks to "raise a PR", "open a pull request", "create a PR", "push and PR", "get this reviewed"…
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.