Borrowing it
Nothing to install: this file belongs to BadC-mpany/lilith-zero. 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/BadC-mpany/lilith-zero/main/.agent/skills/google_oss_management/SKILL.mdgit clone --depth 1 https://github.com/BadC-mpany/lilith-zeroWrote 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/badc-mpany/lilith-zero/google_oss_management)<a href="https://agentmods.dev/skills/badc-mpany/lilith-zero/google_oss_management"><img src="https://agentmods.dev/badge/skills/badc-mpany/lilith-zero/google_oss_management.svg" alt="Measured on agentmods" 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.00036 | $0.01141 |
| Opus 5 | $0.00018 | $0.00571 |
| Sonnet 5 | $0.00007 | $0.00228 |
| Haiku 4.5 | $0.00004 | $0.00114 |
Grade A, and why
google_oss_management 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google-Grade Open Source Project Management (Lilith Edition)
This skill enforces strict engineering rigor for the Lilith project. It mandates that no code is committed without passing the specific CI workflows defined in .github/workflows/ci.yml.
When to use this skill
- Ready to Commit: When the user wants to commit changes, push code, or release a new version.
- Workflow Updates: When the user modifies
.github/workflows/ci.ymlor build configurations (lilith-zero/Cargo.toml,sdk/pyproject.toml). - Documentation: When generating
CHANGELOG.mdupdates based on recent diffs. - Quality Gate: When requested to "finalize" or "polish" a feature for merging.
How to use it
1. Pre-Commit Workflow Validation (The "Green Build" Rule)
Before generating any commit messages, you MUST ask the user to run the relevant verification commands. Do not assume pass.
A. Rust Core Changes (lilith-zero/)
If changes touch lilith-zero/src, lilith-zero/Cargo.toml, or lilith-zero/tests:
- Format & Lint:
cd lilith-zero; cargo fmt --all -- --checkcd lilith-zero; cargo clippy --all-targets --all-features -- -D warnings
- Test:
cd lilith-zero; cargo test --all-features
- Audit (Optional):
cd lilith-zero; cargo audit
B. Python SDK Changes (sdk/)
If changes touch sdk/, sdk/src, or pyproject.toml:
- Lint:
ruff check sdk/src/lilith_zero sdk/tests
- Type Check:
mypy sdk/src/lilith_zero --strict --ignore-missing-imports
- Test:
cd sdk; python -m pytest tests -v
C. Integration/Full System
If changes affect the interaction between Rust and Python:
- Build Rust Binary:
cd lilith-zero; cargo build --release- Note: Set env var:
export LILITH_ZERO_BINARY_PATH="lilith-zero/target/release/lilith-zero"
- Run Integration Test:
- Sandbox Verification:
cd lilith-zero; cargo run --example sandbox_check
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.
- 6d ago First seen · 89 lines · 36 tokens per session scan A 553983307ce4
google_oss_management is a skill published in the GitHub repository BadC-mpany/lilith-zero (23 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 1,141 once invoked, about $0.0002 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-30.
Other skills, from other repositories
devops-pipeline
Configure pre-commit hooks and lean GitHub Actions for shift-left quality assurance. Use when adding or auditing CI/CD to maximize local test coverage and minimize CI cost. Skip for Terraform/K8s, deployment pipelines, or non-GitHub CI providers.
dependabot-consolidator
Consolidate a repository's open Dependabot PRs into one tested branch and PR, grouping by ecosystem and risk, verifying with baseline-diff gates, and closing out on operator approval. Use when a repo has multiple open Dependabot PRs to batch, when consolidating dependency bumps into a single reviewable PR, or when…
shared-tooling-git-hooks
Husky v9 setup, lint-staged v16 patterns, commitlint with conventional commits, CI/production handling, monorepo setup, migration from v8.
git-compact-commits-skill
Concise commits within strict budgets — 72-char subject, 150-word body, semantic grouping. Triggers: compact commit, concise commit, terse commit.
lefthook
Canonical lefthook git-hooks setup: pre-commit (format, check, secret scan) and pre-push (test), each delegating to mise run tasks. Use for git hook configuration.
github
GitHub operations — issues, PRs, commits, code search, CI/CD via gh CLI.