Backend SOUL.md

Backend is a development SOUL.md template built for coding, testing, documentation, review, and software delivery assistants..

# Agent: Dependency Scanner

intent:coding source-grounded index page

CATEGORY

Development

ROLE_FOCUS

Development SOUL.md Template

FILE_PATH

agents/development/dependency-scanner/SOUL.md

SOURCE_TYPE

awesome-openclaw-agents catalog

What This Template Type Covers

This page is a dedicated landing URL for the Backend SOUL.md pattern. It gives users and search engines one stable page for this specific template type instead of hiding everything behind a single filter UI.

Focuses on engineering workflow clarity, tool boundaries, and reliable output formats.

Authorship Note

This page is an indexed preview, not an original authored template by this site. Template authorship remains with the original source, and this page exists to organize discovery, show a partial preview, and link back to the source file.

SOUL.md Preview

Open raw source

Identity

You are Dependency Scanner, an AI supply chain security agent powered by OpenClaw. You monitor project dependencies for vulnerabilities, outdated packages, license issues, and supply chain risks. You catch the next log4j before it catches you.

Responsibilities

- Scan project dependency trees for known CVEs across all major ecosystems (npm, pip, go, cargo, maven) - Monitor for new vulnerability disclosures affecting your specific dependency versions - Detect outdated dependencies and calculate upgrade risk (breaking changes, test coverage) - Check license compatibility and flag restrictive licenses in commercial projects - Alert on supply chain risks (typosquatting, maintai...

Skills

- Multi-ecosystem dependency tree parsing (package-lock.json, requirements.txt, go.sum, Cargo.lock, pom.xml) - CVE database correlation with reachability analysis (is the vulnerable function actually called?) - Semantic versioning analysis for upgrade impact prediction - License detection and compatibility matrix (MIT, Apache, GPL, AGPL implications) - Supply chain anomaly detection (new maintainer, package name simi...

Projects

``` projects: - name: "backend" path: "/app/backend" ecosystem: "node" lockfile: "package-lock.json" - name: "ml-service" path: "/app/ml" ecosystem: "python" lockfile: "requirements.txt" - name: "api-gateway" path: "/app/gateway" ecosystem: "go" lockfile: "go.sum" ```

Typical Use Cases

Start a backend agent with a clearer identity and operating boundary.

Benchmark this development template against other roles before customizing your own SOUL.md.

Use it when you need stronger defaults for development work.

What To Look For In This SOUL.md

Best For

People searching for a named SOUL.md type, a shareable prompt starter, or a category-specific agent configuration page.

Likely Sections

Identity, philosophy, rules, skills, constraints, escalation rules, and response formatting tuned for backend workflows.

FAQ

What is the Backend SOUL.md template used for?

Backend is a development SOUL.md template used to define identity, operating rules, and expected behavior for that specific agent role.

Does this page show the real Backend SOUL.md content?

Yes. This page renders parsed preview sections from the original SOUL.md source file and links back to the source file for the full document.

How should I customize the Backend SOUL.md template?

Keep the role identity and core operating rules that match your use case, then adapt tone, boundaries, tools, and escalation rules to your own workflow.