What is Dayarc Report Issue?

A guided process for preparing and filing a GitHub issue in the Dayarc repository. GitHub issues are records used to report bugs or request changes.

Use it to report a Dayarc bug or feature request, including the expected result, actual result, environment, and reproduction details.

It helps produce a complete, privacy-safe report and prevents an issue from being filed before the user reviews and confirms it.

Dayarc Report Issue — Skill for Claude Code and Codex by YuiZhou

Install

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.

Any agent

npx skills add YuiZhou/dayarc-agent --skill dayarc-report-issue

Clone the repo

git clone --depth 1 https://github.com/YuiZhou/dayarc-agent

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/yuizhou/dayarc-agent/dayarc-report-issue/github.svg)](https://agentmods.dev/skills/yuizhou/dayarc-agent/dayarc-report-issue)

Your own site

<a href="https://agentmods.dev/skills/yuizhou/dayarc-agent/dayarc-report-issue"><img src="https://agentmods.dev/badge/skills/yuizhou/dayarc-agent/dayarc-report-issue/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/yuizhou/dayarc-agent/dayarc-report-issue"><img src="https://agentmods.dev/badge/skills/yuizhou/dayarc-agent/dayarc-report-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 596 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00022	$0.00596
Opus 5	$0.00011	$0.00298
Sonnet 5	$0.00004	$0.00119
Haiku 4.5	$0.00002	$0.00060

Measured 9d ago against content hash 0fa67cb33e46, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

Dayarc Report Issue 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 9d 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.

skills/dayarc-report-issue/SKILL.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

When to Use

User asks to report a bug, file an issue, or request a feature for Dayarc.

Behavior

Classify — Determine if this is a bug or enhancement from conversation context.
Collect — Gather:
- Skill name involved (if applicable)
- What happened vs what was expected
- Brief type (AM/PM/Weekly/Monthly) if relevant
- Version: run git describe --tags --always in ~/.dayarc-agent/
- Platform: $env:OS + PowerShell version
Sanitize — Strip all PII before composing the issue body (see rules below).
Preview — Show the full issue title and body in the terminal. User can edit or cancel.
Confirm — Wait for explicit "yes" before filing. Never file without confirmation.
File — Run:
```
gh issue create --repo YuiZhou/dayarc-agent --title "{title}" --body "{body}"
```
Do NOT add --label. Users don't have label permissions — the triage bot handles labeling.
Report — Show the issue URL to the user.

Issue Body Format

Bug Report

## Bug Report (auto-filed by Dayarc)
**What happened:** [one sentence]
**Expected:** [one sentence]
**Skill:** [name] | **Brief type:** [AM/PM/Weekly/Monthly]
**Version:** [version] | **Platform:** [OS]
### Reproduction context
[Sanitized description of what led to the issue]
### Suggested area
[Likely file(s) or skill(s) involved]

Feature Request

## Feature Request (auto-filed by Dayarc)
**What:** [one sentence]
**Why:** [motivation]
**Related brief/skill:** [if applicable]

PII Sanitization Rules

✅ Include	❌ Exclude
Skill names, version, platform, dates	Email content, subjects, senders
Theme labels ("flagged emails")	Contact names, memory contents, config values
Error description, likely file paths	Repo names, PR titles from user's work

Safety

Dayarc repo only. The target repo YuiZhou/dayarc-agent is hardcoded. Never file issues on any other repository. If the user asks to file an issue elsewhere, refuse.
User confirms. Never file without explicit "yes" after preview.
No PII. Apply sanitization rules strictly. When in doubt, omit.

Read the full file on GitHub · 65 lines

Changes

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.

9d ago First seen · 65 lines · 22 tokens per session scan A 0fa67cb33e46

Subscribe to this mod's changes

Dayarc Report Issue is a skill published in the GitHub repository YuiZhou/dayarc-agent (2 stars, last pushed 14d ago), licensed MIT. It adds 22 tokens to every session and 596 once invoked, about $0.0001 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.

Git and workflow Project management

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

shiplog

Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.

aeonfun/aeon · 46 tokens

llxprt-issue-workflow

Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…

vybestack/llxprt-code · 87 tokens

Dayarc Report Issue