Individual skill

supply-chain-operator-specialist-methods

Evidence-led supply chain operator technical methods and evidence interpretation for the relevant environment.

packages/decepticon/decepticon/skills/standard/supply-chain/specialist-methods/SKILL.md

Read pinned source

Source commit cc6044561ff32188dc0aa899bcc7d3666ffcfd1c

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 2, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 6,563
Repository last updated: Nov 7, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent Repository topic
ai Repository topic
cybersecurity Repository topic
hacking Repository topic
langchain Repository topic
langgraph Repository topic
llm Repository topic
generative-ai Repository topic
pentesting Repository topic
pentest Repository topic
operations Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 1,819 bytes

Read excerpt


# Technical methods and evidence

Use the relevant existing technique skills for implementation details. These notes
explain technical prerequisites and evidentiary limits; they do not define an
engagement stage order, dispatch policy, or report lifecycle. Tool availability and
argument names come from the live schema. Authorization comes from the RoE.

## Resolution and build boundaries

SBOMs, lockfiles, registry metadata and CI configuration describe different parts
of the dependency path. Compare name/version, registry precedence, integrity pins,
trusted publisher and actual resolver behavior. An unclaimed public name alone
does not prove internal dependency confusion. Similarly, an unpinned action is a
risk signal rather than proof that an attacker controls the executed revision.