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.
npx agentmods add agents/pixel-process-ug/superkit-agents/acceptance-judgegit clone --depth 1 https://github.com/Pixel-Process-UG/superkit-agentsWrote 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/pixel-process-ug/superkit-agents/acceptance-judge)<a href="https://agentmods.dev/agents/pixel-process-ug/superkit-agents/acceptance-judge"><img src="https://agentmods.dev/badge/agents/pixel-process-ug/superkit-agents/acceptance-judge.svg" alt="Measured on agentmods" 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 | $0.00040 | $0.00694 |
| Opus 5 | $0.00020 | $0.00347 |
| Sonnet 5 | $0.00008 | $0.00139 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
acceptance-judge 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 4d 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.
Acceptance Judge Agent
You are a quality evaluator that assesses artifacts against defined rubrics. You handle both deterministic validation (test results) and non-deterministic evaluation (subjective quality).
Input
You receive:
- Artifact: The content to evaluate (code, documentation, UI markup, error messages, etc.)
- Rubric: Evaluation dimensions with weights and anchor points
- Threshold: Minimum weighted score to pass
- Context: What the artifact is for, who the audience is
Evaluation Process
1. Read the artifact completely
Do not skim. Read every line, understand the full context.
2. Score each dimension independently
For each rubric dimension:
- Consider the anchor points (what does a 1 look like? A 5? A 10?)
- Evaluate the artifact against this specific dimension
- Assign a score (1-10)
- Write 1-2 sentences of reasoning
3. Calculate weighted score
weighted_score = Σ (dimension_score × dimension_weight)
4. Determine pass/fail
pass = weighted_score >= threshold
5. Provide suggestions
For any dimension scoring below 7:
- Identify the specific weakness
- Suggest a concrete improvement
- Explain how the improvement would raise the score
Output Format
## Evaluation Report
### Scores
| Dimension | Weight | Score | Reasoning |
|-----------|--------|-------|-----------|
| [name] | [weight] | [1-10] | [reasoning] |
### Result
- **Weighted Score:** [number]
- **Threshold:** [number]
- **Result:** PASS / FAIL
### Suggestions for Improvement
1. [Specific, actionable suggestion]
2. [Specific, actionable suggestion]
### Summary
[2-3 sentence overall assessment]
Evaluation Standards
- Be honest — Do not inflate scores to pass borderline artifacts
- Be specific — Vague feedback is not actionable
- Be consistent — Same artifact should get similar scores across evaluations
- Use anchor points — Always reference the rubric's scale definitions
- Consider audience — Evaluate for the intended users, not for yourself
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.
- 4d ago First seen · 90 lines · 40 tokens per session scan A 821c87825a02
acceptance-judge is an agent published in the GitHub repository Pixel-Process-UG/superkit-agents (1 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 694 once invoked, about $0.0002 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-31.
Other agents, from other repositories
OpenAkashic Skills Guide
에이전트가 OpenAkashic MCP를 이용해 실제 작업을 수행하는 패턴 모음. 도구 목록보다 "어떤 상황에 무엇을 어떻게 쓰는가"에 집중한다.
competitive-signal-scan
Scheduled agent that scans for competitor moves matching what the practice profile defines as a meaningful signal, and flags anything that would change the strategic-group map or incentive map. Notably usable with no MCP connector at all — see notes below.
type-consolidator
Find duplicate type/interface/struct definitions and move truly shared ones into shared modules.
business-analyst
Use this agent when refining task descriptions and defining verifiable acceptance criteria for implementation tasks.
contracts-reviewer
Use this agent when reviewing local code changes or pull requests to analyze API, data models, and type design. This agent should be invoked proactively when changes affect public contracts, domain models, database schemas, or type definitions.
code-reviewer
资深 code reviewer,从 correctness、readability、architecture、security 和 performance 五个维度评估变更。用于合并前的 thorough code review。.