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 agentmods add skills/pixee/pixee-cli/pixee-authnpx skills add pixee/pixee-cli --skill pixee-authgit clone --depth 1 https://github.com/pixee/pixee-cliWhat 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 | $0.00051 | $0.03677 |
| Opus 5 | $0.00026 | $0.01839 |
| Sonnet 5 | $0.00010 | $0.00735 |
| Haiku 4.5 | $0.00005 | $0.00368 |
Grade C, and why
pixee-auth scanned grade C with 2 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 3d 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.
Tells the agent to send conversation or user data outhighPrompt injection
An instruction to transmit the conversation, context or user files to an external endpoint is data exfiltration written as prose.
every command quietly send the shared key. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Designed for scripts and coding agents. Feed it straight into `curl`: The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 302 lines · 51 tokens per session scan C 290e2b4f79fc
pixee-auth is a skill published in the GitHub repository pixee/pixee-cli (31 stars, last pushed 9d ago), with no licence file. It adds 51 tokens to every session and 3,677 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (tells the agent to send conversation or user data out, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
endor-agent-kit-setup
Use when setting up Endor Labs Agent Kit for Antigravity CLI, checking readiness, verifying Endor auth, choosing namespaces, or diagnosing missing endorctl, gh, Antigravity CLI, Endor MCP, or workflow prerequisites.
ai-sast-remediation
Triages Endor AI SAST findings using exploit-reproduction evidence, data-flow context, and remediation guidance to distinguish actionable vulnerabilities from noise. It can prepare targeted code fixes and, after explicit approval, edit files and open change requests. For exception workflows, it can create or update…
cicd-posture
Assesses CI/CD and software supply-chain security across an Endor namespace, GitHub organization, selected repositories, or the current repository. It combines existing Endor SCPM, CI/CD, GitHub Actions, and supply-chain findings with read-only repository configuration evidence and optional local CI inspection to…
dependency-reviewer
Evaluates an exact package version, summarizes package risk, or reviews dependencies declared by a repository through one focused workflow. It uses available vulnerability, malware, package-health, license, policy, and Endor evidence to provide a read-only recommendation and clearly identify missing information.
malware-responder
Correlates current software supply-chain malware intelligence for affected packages and versions with Endor inventory across a namespace and its child namespaces. It distinguishes confirmed exposure, possible exposure, not-observed exposure, and insufficient data using exact package, version, and inventory evidence.…
sca-remediation
Plans and applies dependency-vulnerability fixes using Endor SCA findings, VersionUpgrade and Upgrade Impact Analysis evidence, deterministic risk decisions, and local validation. It separates low-risk changes from upgrades requiring deeper compatibility review and requires explicit approval before editing files…