// List all repositories in a GitHub org with their maintainers custom property. Use when the user wants to see who maintains each repo.
Auto-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.
| name | get-maintainers |
| description | List all repositories in a GitHub org with their maintainers custom property. Use when the user wants to see who maintains each repo. |
| argument-hint | [org] |
| allowed-tools | Bash(node *) |
List all repositories in a GitHub organization along with their maintainers custom property value.
Run from the project root:
# List maintainers for all repos in an org
node run.js ./src/getMaintainers.js --org=brave
# With explicit token
node run.js ./src/getMaintainers.js --org=brave --githubToken=ghp_...
| Parameter | Required | Default | Description |
|---|---|---|---|
--org | Yes | - | GitHub organization name |
--githubToken | No | $GITHUB_TOKEN | GitHub PAT |
Returns a Markdown-formatted string with one line per repo that has maintainers:
- https://github.com/org/repo maintainers: user1, user2
.env file with GITHUB_TOKEN (needs org custom properties read + repo metadata permissions)run.js entry point automatically loads .env credentialsmaintainers property are listed