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 bdfinst/agentic-dev-team --skill semantic-scangit clone --depth 1 https://github.com/bdfinst/agentic-dev-teamWrote 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/bdfinst/agentic-dev-team/semantic-scan)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/semantic-scan"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/semantic-scan/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/bdfinst/agentic-dev-team/semantic-scan"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/semantic-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 45 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00074 | $0.00494 |
| Opus 5.5 | $0.00030 | $0.00198 |
| Sonnet 5.5 | $0.00015 | $0.00099 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
semantic-scan 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 1mo 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.
What it actually says
Semantic Scan
Role: worker.
Worker constraints
- Detect and report duplicates; do not refactor.
- Run incrementally (git-diff based) after the first scan.
- Be concise. Report the duplicate table with file:line refs, no narration.
Steps
1. Parse arguments
Capture the optional path and flags from $ARGUMENTS.
2. Delegate
Invoke the semantic-duplication-scan skill.
Graph-assisted discovery. Prefer CodeGraph/Repowise over raw Grep/Read
when locating and comparing candidate implementations — Repowise's semantic
search is especially well suited to finding duplicate implementations across
layers. See
knowledge/codegraph-vs-graphify.md
for tool selection and the fallback contract.
3. Report
Output the duplicate report.
Apply the guidelines defined in skills/semantic-duplication-scan/SKILL.md to the current task. Read the skill file and follow its process flow, pre-filter rules, annotation procedure, clustering strategy, and report format.
Flags
[path]— Optional subdirectory to scope the scan. Only files under this path are re-annotated; out-of-scope register entries are preserved.--full— Force full-scan mode regardless of whether a register exists. Bypasses the shallow-clone pre-flight check. Use whenlastScanCommitis stale or after a major restructuring.--no-opus— Skip Opus canonical resolution for ambiguous clusters. Ambiguous clusters are reported ascanonical: ambiguous — human review requiredinstead of triggering an Opus call. Use in cost-sensitive environments (CI, personal accounts).
Apply this skill to: $ARGUMENTS
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.
- 1mo ago First seen · 54 lines · 74 tokens per session scan A 139b6f9a84f9
semantic-scan is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 74 tokens to every session and 494 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other skills, from other repositories
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
gsd-ns-review
quality gates | code review debug audit security eval ui.
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
cleanup-code-inspections
Reduce technical debt and improve code quality by systematically resolving static analysis warnings.
superlint
This skill describes the mandatory standard operating procedure for using our internal SuperLint tool. Use this when tasks require fixing code quality issues according to corporate standards.