Files

Defame1297 675ba40238 feat(kyberforge): restructure agent-audit for plugin-scope apm agents

Validates the new single-file .apm/agents/<name>.agent.md shape agent-author
now produces at plugin/APM scope: frontmatter allowlist (name/description/
model only, from a new apm-agent-allowlist entry in field-inventory.md),
no counterpart derivation, and Pair Consistency dropped from that scope's
report entirely (nothing to pair by design). Adds a plugin/APM-scope-only
SUGGESTION when an agent's description/body implies a tool restriction or
Claude-only behavior the vendor-neutral frontmatter can no longer express
(ADR-0016).

Scope detection in both validate.sh and validate-provenance.sh switches
from a flat plugin.json/.claude-plugin/plugin.json check to a walk-up for
the nearest ancestor apm.yml with a top-level type: field, skipping
type:-less marketplace-only manifests — full switch, no dual-mode fallback
to the old plugin.json signal. validate-provenance.sh's walk-up was fixed
to match validate.sh's (it still used the old plugin.json check, and its
counterpart-merge logic was rewritten to read a single file's source_keys
instead of merging a CC+Copilot pair, since plugin/APM scope has no
counterpart). Project/user scope validation is unchanged in both scripts.

Refs: #89

2026-08-11 18:05:33 +00:00

README.md

feat(kyberforge): add agent-audit skill (closes #11 )

2026-07-04 10:06:37 +00:00

vale-wrap.sh

refactor(kyberforge): consolidate vale-wrap.sh's config parsing and subprocess spawns

2026-08-09 20:14:23 +00:00

validate-provenance.sh

feat(kyberforge): restructure agent-audit for plugin-scope apm agents

2026-08-11 18:05:33 +00:00

validate.sh

feat(kyberforge): restructure agent-audit for plugin-scope apm agents

2026-08-11 18:05:33 +00:00

README.md

scripts/

Executable code bundled with this skill. Agents run scripts in this directory to perform repeatable operations rather than reinventing the logic each run.

When to add a script

Add a script when agents independently reinvent the same logic across runs — building the same parser, chart, or validation routine from scratch each time. Bundle it here once, tested and reliable.

Script requirements (agentskills.io)

Scripts must be designed for non-interactive, agentic execution:

No interactive prompts — agents run in non-interactive shells. Accept all input via flags, env vars, or stdin. A script that blocks on TTY input hangs indefinitely.
Expose --help — this is how agents learn your script's interface. Keep the output concise; it enters the agent's context window.
Structured output — write data (JSON, CSV, TSV) to stdout. Write progress, warnings, and diagnostics to stderr.
Idempotent — prefer "create if not exists" over "create and fail on duplicate". Agents may retry on failure.
Meaningful exit codes — 0 for success, non-zero for failure. Use distinct codes for different failure types; document them in --help.
Dry-run support — add --dry-run for destructive operations.

Self-contained scripts

Bundle dependencies inline so the agent can run the script with a single command.

Python (PEP 723 + uv):

# /// script
# dependencies = ["requests>=2.31,<3"]
# requires-python = ">=3.11"
# ///
import requests

uv run scripts/my-script.py

If no scripts are needed

Delete this README and the scripts/ directory entirely.