// Fetch and parse a JSON config file from a GitHub repository. Use when the user wants to read a configuration file from a remote repo.
| name | get-config |
| description | Fetch and parse a JSON config file from a GitHub repository. Use when the user wants to read a configuration file from a remote repo. |
| argument-hint | [owner] [repo] [path] |
| allowed-tools | Bash(node *) |
Fetch and JSON-parse a configuration file from a GitHub repository via the contents API.
Run from the project root:
# Fetch a config file
node run.js ./src/getConfig.js --owner=brave --repo=brave-browser --path=.github/security-action.json
# With debug logging
node run.js ./src/getConfig.js --owner=brave --repo=brave-browser --path=.github/security-action.json --debug=true
| Parameter | Required | Default | Description |
|---|---|---|---|
--owner | Yes | - | Repository owner |
--repo | Yes | - | Repository name |
--path | Yes | - | File path within the repo |
--githubToken | No | $GITHUB_TOKEN | GitHub PAT |
--debug | No | false | Enable verbose logging |
Returns the parsed JSON object from the file, or {} on error (file not found, invalid JSON, etc.).
.env file with GITHUB_TOKENrun.js entry point automatically loads .env credentials.github/security-action.json per-repo configurationAuto-detect top maintainers for each repo in an org and set the maintainers custom property via the GitHub API. Use when the user wants to populate or update maintainer metadata.
Validate metadata fields (author, source, category) in opengrep/semgrep YAML rule files. Use when the user wants to lint or check rule quality.
Clean up stale security-action Slack messages based on review signals (reactions, label removal, resolved threads). Use when the user wants to clean old notifications from a Slack channel.
Delete Slack messages from a channel filtered by bot username and repository names. Use when the user wants to bulk-delete bot messages for specific repos.
Auto-dismiss Dependabot alerts matching configurable hotwords (e.g. DoS) or a GHSA/CVE dismiss list. Use when the user wants to bulk-dismiss low-priority Dependabot alerts.
Scan org repos for open Dependabot alerts at or above a severity threshold and build notification messages for maintainers. Use when the user wants to check or nudge about Dependabot vulnerabilities.