CMN-C1-185 — Legacy System CLI Integration & Agent-Native Compatibility Validation Agent

Category: Cat 1 (single technical capability, use-case-agnostic) Industry: Common (industry-agnostic)

Overview

Static validation of a shell or database command before an agent hands it to a legacy system. Given a JSON payload such as {"command": "cp a.txt b.txt", "target_encoding": "ascii"} (or a bare command string), the agent checks that the command tokenises with balanced quotes, that it is representable in the target legacy encoding, whether it matches non-idempotent patterns (append, mkdir without -p, INSERT without ON CONFLICT) and whether it matches destructive patterns (rm -rf, DROP, DELETE without WHERE), then returns valid, verdict, blocking, failed_checks, findings and the per-check results. All checks are deterministic pattern rules; the command is never executed and no LLM is involved. A destructive match sets blocking so an integration gate can stop the call, and the report carries a disclaimer that the pattern checks are conservative and not a substitute for testing.

This is an agent template built with the AGENTIC STAR development platform and the AgentCore Framework. It is intended to be taken as a starting point: fork it, adapt it to your own data and policies, and run it inside your own AGENTIC STAR deployment.

Requirements

This template does not run standalone. It requires:

Requirement	Notes
AGENTIC STAR platform	The agent connects to the platform at start-up. Without it, start-up fails immediately (see Behaviour without the platform below). Deployment guides and API documentation: AGENTIC STAR Developers
AgentCore Framework (agenticstar-agentcore)	Installed from PyPI as a dependency.
Python	3.11 or later (requires-python = ">=3.11")

pip install -e .

Behaviour without the platform

The framework is designed to run only on AGENTIC STAR. There is no fallback or degraded mode. If the platform is unreachable or the SDK version does not match, the agent raises PlatformRequired during graph compile / start-up preflight rather than starting in a partially working state. This is intentional — a half-running agent is worse than one that refuses to start.

Quick Start

python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
python -m pytest tests/ -v

Tests run without a platform connection. Running the agent itself does not.

Project Structure

src/          agent implementation (nodes, services, schemas)
tests/        unit, integration and boundary tests
config/       agent configuration
docs/         design and operational documentation

See docs/02_design.md for the design and docs/03_test_spec.md for the test specification.

Customising

1. Adjust config/ for your own environment and policies.
2. Replace the knowledge sources and sample data with your own.
3. Review the node implementations under src/nodes/ for domain-specific logic.
4. Re-run the test suite.

License

MIT — see LICENSE.

Status of this repository

This template is published as is, by its individual author, under the MIT license. It carries no warranty and no support commitment, and no organisation stands behind its behaviour or fitness for any purpose. Issues and pull requests may or may not receive a response; that is at the sole discretion of the repository owner.