Skip to content
Back to skills

Agent Output Hygiene Ops

ASecurity

Audit and remediate AgentSystem cron output hygiene by detecting raw tool logs, stack traces, and noisy summaries. Use when jobs leak 403/429/internal details, summaries are not user-safe, or post-change validation is required.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
ai-agentsbash

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add mahsumaktas/agent-evolution-kit --skill agent-output-hygiene-ops --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agent Output Hygiene Ops?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agent Output Hygiene Ops
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mahsumaktas-agent-output-hygiene-ops/badge)](https://www.skillsdirectory.com/skills/mahsumaktas-agent-output-hygiene-ops)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: agent-system-output-hygiene-ops
description: Audit and remediate AgentSystem cron output hygiene by detecting raw tool logs, stack traces, and noisy summaries. Use when jobs leak 403/429/internal details, summaries are not user-safe, or post-change validation is required.
---

# AgentSystem Output Hygiene Ops

Run this skill when cron summaries must stay concise and safe for user-facing channels.

## Quick Start

1. Run hygiene audit:
```bash
bash scripts/hygiene_audit.sh --run-suite
```

2. If leaks exist, patch top leaking jobs using `references/prompt-remediation.md`.

3. Smoke-test patched jobs:
```bash
agent-system cron run <job-id> --expect-final --timeout 480000
agent-system cron runs --id <job-id> --limit 2 --expect-final
```

## Workflow

1. Run `scripts/hygiene_audit.sh` and identify highest-frequency leaking job IDs.
2. Prioritize jobs leaking raw tool output (`Exec`, `stack trace`, `raw JSON`, `403/429` payloads).
3. Apply strict output contract to prompt:
- ban raw logs and internal diagnostics
- force compact final format or `NO_REPLY`
- prefer deterministic local fallback over noisy web-search errors
4. Re-run patched jobs and confirm the latest run is clean.
5. Re-run health suite and record report paths.

## Resources

- `scripts/hygiene_audit.sh`: summarizes leak-heavy jobs from latest health report.
- `references/prompt-remediation.md`: safe prompt patch template and command pattern.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.