project_tools

A set of commands for adding, viewing, changing, and removing projects in a workflow configuration file. It can inspect a project folder to suggest its language, Git branch, repository, lint command, and test command.

In plain words
What is it for?
Use it to register projects, review configured projects, detect settings from a folder, and maintain project workflow entries.
Why use it?
It avoids manually keeping project paths and development settings up to date in config.json.

Command

Install

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.

agentmods
npx agentmods add commands/dmzoneill/redhat-ai-workflow/project_tools
Clone the repo
git clone --depth 1 https://github.com/dmzoneill/redhat-ai-workflow
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,404 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01404
Opus 5 $0.00000 $0.00702
Sonnet 5 $0.00000 $0.00281
Haiku 4.5 $0.00000 $0.00140

Measured 3d ago against content hash e1252c18901f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

project_tools 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 3d 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.

docs/commands/project_tools.md · 223 lines

How it starts

The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project Tools

Tools for managing projects in config.json.

Overview

These tools help you add, list, update, and remove projects from the workflow configuration. They support auto-detection of project settings from the filesystem.

Tools

project_list

List all configured projects.

project_list()

Shows:

  • Project name and path
  • GitLab and Jira configuration
  • Default branch
  • Status (✅ if path exists, ❌ if missing)

project_detect

Auto-detect project settings from a directory.

project_detect(path="/path/to/project")

Detects:

  • Language: Python, JavaScript, Go, Rust, Java
  • Default branch: From git remote HEAD
  • GitLab remote: From git origin URL
  • Lint command: Based on config files (pyproject.toml, package.json, etc.)
  • Test command: Based on test framework detection
  • Scopes: From directory structure

Returns a suggested config entry that can be used with project_add.

project_add

Add a new project to config.json.

project_add(
    name="my-project",
    path="/home/user/src/my-project",
    gitlab="org/my-project",
    jira_project="AAP",
    jira_component="My Component",  # optional
    lint_command="",                # auto-detected if empty
    test_command="",                # auto-detected if empty
    default_branch="main",          # auto-detected if empty
    konflux_namespace="",           # optional
    scopes="api,core,tests",        # comma-separated, auto-detected if empty
    auto_detect=True                # enable auto-detection
)

If auto_detect=True (default), empty fields will be populated from the project directory.

project_update

Update an existing project's configuration.

project_update(
    name="my-project",
    lint_command="ruff check .",    # only updates provided fields
    test_command="pytest -v"
)

Only updates fields that are provided (non-empty).

project_remove

Remove a project from config.json.

project_remove(name="my-project")           # shows confirmation prompt
project_remove(name="my-project", confirm=True)  # actually removes

Read the full file on GitHub · 223 lines

Changes

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.

  1. 3d ago First seen · 223 lines · 0 tokens per session scan A e1252c18901f

Subscribe to this mod's changes

project_tools is a command published in the GitHub repository dmzoneill/redhat-ai-workflow (5 stars, last pushed 23d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,404 tokens. 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-31.