DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to import asset data from ScopeSentry into the asset graph with Autonomous Pentest Agent

Connect ScopeSentry with its address and API key, then import domains, IPs, and ports by project or task.

Authorization notice. Autonomous Pentest Agent is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Credentials. The ScopeSentry API key is stored in the agent so it can sync, so use a key with the least access you need.

Who it is forA pentest lead who already collects assets with ScopeSentry and wants the agent to start from that inventory.

The problemRe-collecting the same domains, subdomains, and ports by hand wastes time and can miss what the scanner already found.

The outcomeAssets in the Autonomous Pentest Agent asset graph, grouped by company scope, ready for the agent to explore.

What you need first

  • A PostgreSQL database, or Docker so the install script can start one
  • An LLM API key: ANTHROPIC_API_KEY or OPENAI_API_KEY, or the key entered later in the UI's LLM 配置 page
  • Docker for the one-click install path, or the Go toolchain and Node.js for a local build from source
  • Written authorization to test the target systems

Steps

  1. Make sure a running ScopeSentry instance is reachable and you have its API key.
  2. Open the 资产同步 page in the agent UI.
  3. Enter the ScopeSentry address and API key to connect the data source.
  4. Choose a project or task, then select the asset types to sync such as 域名, 子域, IP, 端口, 站点, or 端点.
  5. Click import and check the 资产 page for the new assets.

Prompt for your agent

Using the repo kutukam/autonomous-pentest-agent, connect it to a ScopeSentry instance at <scopesentry-url> with the API key <api-key>. Import the assets from project <project-name> and report the count of assets in the asset graph. Verify by listing the imported assets in the 资产 page before you start any exploration.

Caveat. This use case needs a separate ScopeSentry deployment, which the README links to but does not set up for you.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page