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 skills add Samurai-goose/SPECTER-The-Illusive-Security-Protocol --skill ci-cd-supply-chain-securitygit clone --depth 1 https://github.com/Samurai-goose/SPECTER-The-Illusive-Security-ProtocolWrote 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/samurai-goose/specter-the-illusive-security-protocol/ci-cd-supply-chain-security)<a href="https://agentmods.dev/skills/samurai-goose/specter-the-illusive-security-protocol/ci-cd-supply-chain-security"><img src="https://agentmods.dev/badge/skills/samurai-goose/specter-the-illusive-security-protocol/ci-cd-supply-chain-security/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/samurai-goose/specter-the-illusive-security-protocol/ci-cd-supply-chain-security"><img src="https://agentmods.dev/badge/skills/samurai-goose/specter-the-illusive-security-protocol/ci-cd-supply-chain-security.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.00051 | $0.01942 |
| Opus 5 | $0.00026 | $0.00971 |
| Sonnet 5 | $0.00010 | $0.00388 |
| Haiku 4.5 | $0.00005 | $0.00194 |
Grade A, and why
ci-cd-supply-chain-security 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 11d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD & Supply Chain Security
Purpose
Audit continuous integration/delivery pipelines and software supply chains for compromise vectors. CI/CD systems are high-value targets: they hold deployment credentials, build artifacts, and have write access to production. Supply chain attacks (dependency confusion, typosquatting, artifact tampering) bypass traditional application security controls entirely.
Triggers
- CI/CD configuration files found in repository (.github/workflows, .gitlab-ci.yml, Jenkinsfile)
- User requests pipeline security review
- Dependency audit surfaces supply chain concerns
- New deployment pipeline being configured
- Security governance engagement includes infrastructure
Required Inputs
| Input | Description | Required |
|---|---|---|
governance_context |
Active engagement governance record | Yes |
pipeline_configs |
CI/CD config files (workflow YAML, Jenkinsfile, etc.) | Yes |
ci_platform |
GitHub Actions, GitLab CI, Jenkins, CircleCI, etc. | Auto-detected |
package_registries |
npm, PyPI, Docker Hub, internal registries in use | Recommended |
deployment_targets |
Where artifacts deploy to (cloud, K8s, servers) | Recommended |
Workflow
-
Scope Verification — Confirm CI/CD systems and registries are within authorized scope.
-
Pipeline Configuration Review
GitHub Actions:
- Review all workflow files in
.github/workflows/ - Check
pull_request_targettrigger (runs with write access on untrusted PR) - Check
workflow_runchaining for privilege escalation - Review
permissions:block — avoid default write-all - Check for
${{ github.event.*.body }}or similar injection inrun:steps - Verify actions pinned to SHA (not tag/branch — mutable references)
- Review third-party actions for trust (verified publisher, source audit)
- Check
GITHUB_TOKENpermissions scope - Review secret access: which jobs/steps can access which secrets?
- Check for
if:conditions that can be bypassed - Review artifact upload/download for path traversal
- Review all workflow files in
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.
- 11d ago First seen · 208 lines · 51 tokens per session scan A 2495b7ec299a
ci-cd-supply-chain-security is a skill published in the GitHub repository Samurai-goose/SPECTER-The-Illusive-Security-Protocol (2 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 1,942 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
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.