context safety score
A score of 49/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
credential exposure
Found 16 secret pattern match(es) in repository files
supply chain
Found 2 install-script pattern(s) in documentation (likely install instructions, not executable)
supply chain
Found 2 remote script pattern(s) in documentation (likely install instructions, not executable)
scope violation
SKILL.md is completely empty (0 lines) while metadata claims 7.69M installs and 29.4K stars. A skill with no tool definitions, no parameters, and no documentation provides zero functionality. This is either a name-squatted placeholder for the high-trust name 'k8s-security-policies' or a broken listing. The empty skill file means its content could be populated later with malicious definitions after trust is established. (location: SKILL.md)
supply chain
The skill_description field contains 'width=device-width, initial-scale=1' — an HTML viewport meta tag value, not a legitimate skill description. This indicates metadata was either scraped from an HTML page, injected, or fabricated rather than authored as a genuine skill. Combined with the empty SKILL.md, this suggests the listing is not a real, functioning skill but a placeholder or corrupted entry with artificially associated repository metrics (29K stars likely belong to the repo 'wshobson/agents', not this specific skill). (location: metadata.json:skill_description)
supply chain
Repository 'wshobson/agents' has high metrics (29K stars, 3.2K forks, 7.69M installs) but is NOT listed on the registry (listed_on_registry: false). The generic repo name 'agents' combined with a specific skill name 'k8s-security-policies' and empty SKILL.md suggests the skill is borrowing credibility from an unrelated or loosely-related popular repository. Agents installing this skill based on repository-level trust signals would get an empty, non-functional skill. (location: metadata.json)
curl https://api.brin.sh/skill/wshobson%2Fagents%2Fk8s-security-policiesCommon questions teams ask before deciding whether to use this skill in agent workflows.
wshobson/agents/k8s-security-policies currently scores 49/100 with a suspicious verdict and medium confidence. The goal is to protect agents from high-risk context before they act on it. Treat this as a decision signal: higher scores suggest lower observed risk, while lower scores mean you should add review or block this skill.
Use the score as a policy threshold: 80–100 is safe, 50–79 is caution, 20–49 is suspicious, and 0–19 is dangerous. Teams often auto-allow safe, require human review for caution/suspicious, and block dangerous.
brin evaluates four dimensions: identity (source trust), behavior (runtime patterns), content (malicious instructions), and graph (relationship risk). Analysis runs in tiers: static signals, deterministic pattern checks, then AI semantic analysis when needed.
Identity checks source trust, behavior checks unusual runtime patterns, content checks for malicious instructions, and graph checks risky relationships to other entities. Looking at sub-scores helps you understand why an entity passed or failed.
brin performs risk assessments on external context before it reaches an AI agent. It scores that context for threats like prompt injection, hijacking, credential harvesting, and supply chain attacks, so teams can decide whether to block, review, or proceed safely.
No. A safe verdict means no significant risk signals were detected in this scan. It is not a formal guarantee; assessments are automated and point-in-time, so combine scores with your own controls and periodic re-checks.
Re-check before high-impact actions such as installs, upgrades, connecting MCP servers, executing remote code, or granting secrets. Use the API in CI or runtime gates so decisions are based on the latest scan.
Learn more in threat detection docs, how scoring works, and the API overview.
Assessments are automated and may contain errors. Findings are risk indicators, not confirmed threats. This is a point-in-time assessment; security posture can change.
integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.