[Safe Outputs Conformance] MCE-001: add_comment tool description missing explicit "50 link" limit phrase
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 84/100
Research direction
Start with the add_comment description in pkg/workflow/js/safe_outputs_tools.json and check whether it is generated from a Go source template, as the issue suggests. Update the source description to say “maximum 50 links,” then run bash scripts/check-safe-outputs-conformance.sh; done means MCE-001 passes.
Written by the indexing model from the issue text.
Description
Conformance Check Failure
Check ID: MCE-001
Severity: MEDIUM
Category: MCP Constraint Enforcement (Section 8.3 MCE2)
Problem Description
The safe-outputs conformance checker's MCE-001 check requires the add_comment tool description in pkg/workflow/js/safe_outputs_tools.json to literally contain the phrase "50 link" so agents can see the link-count ceiling at a glance. The current description discloses the same constraint using different wording — "the configured max-links URL occurrences in agent content (default: 50; generated footer and metadata links excluded)" — so the limit is present but not in the exact phrasing the check (and by extension, a quick-scanning agent) expects.
Affected Components
- Files:
pkg/workflow/js/safe_outputs_tools.json(tool-leveldescriptionforadd_comment, ~line 525) - Checker:
scripts/check-safe-outputs-conformance.sh(MCE-001,check_mce_constraint_disclosure)
<b>🔍 Current vs Expected Behavior</b>
Current Behavior
The add_comment description states the link ceiling as "the configured max-links URL occurrences in agent content (default: 50; ...)" — functionally correct but not literally matching the 50 link substring the checker greps for.
Expected Behavior
Per spec Section 8.3 MCE2, add_comment MUST surface its 65536-character, 10-mention, and 50-link constraints in its tool description in agent-legible terms. The description should state the link limit as something like "maximum 50 links" so both the automated check and a skimming agent recognize it unambiguously.
Remediation Steps
- In
pkg/workflow/js/safe_outputs_tools.json, reword theadd_commenttool description's link-limit clause to include an explicit "maximum 50 links" (or equivalent "50 link" phrasing) alongside the existing max-links explanation. - Check whether this description is generated from a Go source template rather than hand-edited JSON, and make the change at the source if so, then regenerate.
- Re-run the conformance checker to confirm MCE-001 passes.
Verification
After remediation, verify the fix by running:
bash scripts/check-safe-outputs-conformance.sh
The check MCE-001 should pass without errors.
References
- Safe Outputs Specification: docs/src/content/docs/specs/safe-outputs-specification.md
- Conformance Checker: scripts/check-safe-outputs-conformance.sh
- Run: §39101480539
Generated by ✅ Daily Safe Outputs Conformance Checker · claude · agent · 59 AIC · ⌖ 0.818 AIC · ⊞ 5.3K · ◷
- expires on Oct 18, 2026, 9:48 PM UTC-08:00
- Dominant language
- Go
- Stars
- 5.4k
- Forks
- 584
- Avg merge
- 3h 16m
- Merged PRs (30d)
- 829
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/gh-aw
-
agent-research
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
windows workflow
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
cookie sergo
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/gh-aw#69613 · 1 comment ·
Maintainers usually reply within 1 day
-
MCP Gateway rejects digest-pinned container images: embedded JSON schema disagrees with containerPatternPossibly taken @pelikhan claimed this today. Openai-inspected
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
goroutineresourceleak (81st linter): paren_unwrap_gap across lock/cancel/channel detection, day oneOpencookie sergo
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/gh-aw#68591 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
dataiku/kiji-proxy#635 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
hyperledger-firefly/signer#126 ·
-
agent-review-finding chore
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
jordansmall/spindrift#5748 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Resource links written as host:port without a scheme are brokenPossibly taken @RaphaelFakhri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day