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 harness/harness-skills --skill configure-repo-scangit clone --depth 1 https://github.com/harness/harness-skillsWrote 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/harness/harness-skills/configure-repo-scan)<a href="https://agentmods.dev/skills/harness/harness-skills/configure-repo-scan"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/configure-repo-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/harness/harness-skills/configure-repo-scan"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/configure-repo-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00103 | $0.02009 |
| Opus 5 | $0.00051 | $0.01005 |
| Sonnet 5 | $0.00021 | $0.00402 |
| Haiku 4.5 | $0.00010 | $0.00201 |
Grade A, and why
configure-repo-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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- configure-repo-scan — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure Repo Scan
Add code scanning steps to existing Harness pipelines using STO security scanners.
Instructions
Step 1: Establish Scope and Pipeline Context
Ask the user for the organization, project, and pipeline identifier if not already known. This skill only works with existing pipelines.
Once you have the identifiers, fetch the pipeline definition:
Call MCP tool: harness_get
Parameters:
resource_type: "pipeline"
resource_id: "<pipeline_identifier>"
org_id: "<organization>"
project_id: "<project>"
Step 2: Extract Repository Connector from Pipeline
Parse the pipeline YAML from Step 1 to automatically identify the repository connector used in the pipeline.
Look for the connector reference in the pipeline structure:
- For v0 pipelines: Check
pipeline.properties.ci.codebase.connectorRef - For v1 pipelines: Check the codebase connector in the pipeline configuration
If no connector is found in the pipeline, inform the user that the pipeline does not have a codebase configuration and cannot proceed with repo scanning.
Step 3: Analyze Pipeline Structure
Parse the pipeline YAML from Step 1 to identify:
- All stages (CI, Deployment, Approval, Custom)
- All steps within each stage
- Existing security scanning steps (if any)
Present a structured view to the user showing:
Pipeline: <name>
Stage 1: <stage_name> (type: <stage_type>)
- Step 1: <step_name> (type: <step_type>)
- Step 2: <step_name> (type: <step_type>)
...
Stage 2: <stage_name> (type: <stage_type>)
- Step 1: <step_name> (type: <step_type>)
...
Ask the user where they would like to insert the code scanner step:
- "Before which step?" or "After which step?" or "At the end of which stage?"
- Provide suggestions (e.g., "I recommend adding it after the build step but before deployment")
Step 4: Recommend Scanner Type
Present the available SAST scanners supported in Harness STO:
Available SAST Scanners:
- Harness Code (default - native Harness scanner)
- Bandit (open-source, Python)
- Black Duck (by Synopsys)
- Brakeman (open-source, Ruby)
- Checkmarx
- Checkmarx One
- Coverity (open-source)
- CodeQL
- FOSSA
- GitHub Advanced Security
- Mend (formerly WhiteSource)
- Semgrep (open-source)
- Snyk
- SonarQube
- Veracode
- Wiz
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 271 lines · 103 tokens per session scan A d16d6460307e
configure-repo-scan is a skill published in the GitHub repository harness/harness-skills (106 stars, last pushed 3d ago), licensed Apache-2.0. It adds 103 tokens to every session and 2,009 once invoked, about $0.0005 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-30.
Other skills, from other repositories
github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
secrets-management
Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.
deployment-pipeline-design
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use this skill when designing zero-downtime deployment pipelines, implementing canary rollout strategies, setting up multi-environment promotion workflows, or debugging failed deployment gates in CI/CD.
gitlab-ci-patterns
Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.
airflow-dag-patterns
Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.