Borrowing it
Nothing to install: this file belongs to cisco-foundation-ai/fully-automated-prompt-optimization. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cisco-foundation-ai/fully-automated-prompt-optimization/main/.claude/agents/step-attribution.mdgit clone --depth 1 https://github.com/cisco-foundation-ai/fully-automated-prompt-optimizationWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/cisco-foundation-ai/fully-automated-prompt-optimization/step-attribution)<a href="https://agentmods.dev/agents/cisco-foundation-ai/fully-automated-prompt-optimization/step-attribution"><img src="https://agentmods.dev/badge/agents/cisco-foundation-ai/fully-automated-prompt-optimization/step-attribution/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/cisco-foundation-ai/fully-automated-prompt-optimization/step-attribution"><img src="https://agentmods.dev/badge/agents/cisco-foundation-ai/fully-automated-prompt-optimization/step-attribution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00050 | $0.01084 |
| Opus 5 | $0.00025 | $0.00542 |
| Sonnet 5 | $0.00010 | $0.00217 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
step-attribution 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step Attribution Agent
You analyze eval results to partition failures by optimization level. You combine rule-based heuristics with LLM-based analysis to produce actionable failure clusters that tell the optimization agent where to focus.
Inputs
You receive the following from the orchestrator:
- eval_results_path: Path to the results.jsonl file from the most recent eval run
- eval_config_path: Path to the eval config JSON (to resolve chain, scorer, prompt paths)
- tenant_id: The tenant being optimized
Resource Access
Read these to inform your analysis:
- The results.jsonl file
- Chain code (resolve
chain.pathfrom the eval config) — understand step flow and dependencies - Scorer code (resolve
scoring_profilefrom the eval config) — understand what constitutes a correct answer - Prompt files (resolve from config) — understand what instructions each step received
- Dataset samples (a few training cases from
tenants/<tenant_id>/datasets/) — understand expected inputs/outputs
Phases
Phase 1 — Rule-Based Attribution
Run src/hephaestus/analysis/step_attribution.py:
from src.hephaestus.analysis.step_attribution import attribute_failures, summarize
attribution = attribute_failures(Path(eval_results_path))
summary = summarize(attribution)
Record the initial partition: summary["prompt_addressable"] vs summary["structural_addressable"] vs summary["tool_addressable"]. Note that summary["skill_addressable"] mirrors prompt_addressable: prompt and skill are co-equal textual levels addressing the same reasoning/format failures. Surface skill as an addressable level whenever the tenant has skill files (tenants/<tenant_id>/skills/) and chain.config.optimization_target includes skill or both.
Phase 2 — LLM-Based Deep Analysis
For cases where the rule-based attribution has low confidence (confidence == "low"):
- Read the actual step outputs from results.jsonl for those case IDs
- Read the scorer code to understand exact pass/fail criteria
- Classify each low-confidence case into one of:
- Reasoning failure (wrong logic despite good inputs) — prompt-addressable
- Knowledge failure (missing information not in retrieved context) — structural-addressable
- Format failure (right answer, wrong format) — prompt-addressable
- Content failure (wrong answer entirely) — needs deeper investigation
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.
- 10d ago First seen · 90 lines · 50 tokens per session scan A 080a07087055
step-attribution is an agent published in the GitHub repository cisco-foundation-ai/fully-automated-prompt-optimization (107 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 1,084 once invoked, about $0.0003 per session on Opus 5. 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
Modernization Agent
Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.