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 skills add YuiZhou/dayarc-agent --skill dayarc-add-connectorgit clone --depth 1 https://github.com/YuiZhou/dayarc-agentWrote 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/skills/yuizhou/dayarc-agent/dayarc-add-connector)<a href="https://agentmods.dev/skills/yuizhou/dayarc-agent/dayarc-add-connector"><img src="https://agentmods.dev/badge/skills/yuizhou/dayarc-agent/dayarc-add-connector/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/skills/yuizhou/dayarc-agent/dayarc-add-connector"><img src="https://agentmods.dev/badge/skills/yuizhou/dayarc-agent/dayarc-add-connector.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.00041 | $0.02719 |
| Opus 5 | $0.00020 | $0.01359 |
| Sonnet 5 | $0.00008 | $0.00544 |
| Haiku 4.5 | $0.00004 | $0.00272 |
Grade A, and why
Dayarc Add Connector 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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Trigger this skill when the user says anything like:
- "I need to connect Jira"
- "Add a connector for ADO / Linear / Slack"
- "Set up Jira integration"
- "I want Dayarc to check my Jira tickets"
- "Connect {tool} with requirements …"
Do NOT trigger this skill for the built-in work-iq or github connectors — those are pre-configured.
Overview
This skill has five phases:
- Collect — understand what the user needs from this tool
- Generate — produce a custom COLLECT skill tailored to those requirements
- Install — write the skill file to
~/.copilot/skills/(upgrade-safe location) - Register — update
mcp.json+config.jsonso the COLLECT step uses it - Confirm — show the user what was configured and what to expect in their briefs
Phase 1: Collect Requirements
Ask the following questions one at a time. Stop asking if the user provides answers upfront.
1a. Tool name
If not already clear from the user's request, confirm: "Which tool are we connecting — Jira, Azure DevOps, Linear, Slack, or something else?"
1b. MCP server package
Ask: "What npm (or pip/Docker) package provides the MCP server for {tool}? For example, @modelcontextprotocol/server-jira."
For common tools, suggest defaults:
| Tool | Suggested MCP package |
|---|---|
| Jira | @modelcontextprotocol/server-jira |
| Azure DevOps | @modelcontextprotocol/server-azure-devops |
| Linear | @modelcontextprotocol/server-linear |
| Slack | @modelcontextprotocol/server-slack |
If the user doesn't know, tell them to check modelcontextprotocol/servers or ask the tool's community.
1c. Signal categories
Ask: "What should Dayarc collect from {tool}? Choose all that apply:"
Present as a numbered list:
assigned_items— open tasks/tickets assigned to you (→ AM Today's Plan)notifications— new @mentions, review requests, assignments (→ AM Today's Plan + Signals)flagged_items— items you've starred or prioritized (→ AM Today's Plan)sent_activity— work you've done: comments, transitions, created items (→ PM What I Did)recent_docs— recently edited documents or wikis (→ PM What I Did)calendar— meetings or events (→ AM/PM calendar section)saved_items— items you've bookmarked or saved for later (→ AM Today's Plan)
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 · 279 lines · 41 tokens per session scan A b544ddb6b198
Dayarc Add Connector is a skill published in the GitHub repository YuiZhou/dayarc-agent (2 stars, last pushed 15d ago), licensed MIT. It adds 41 tokens to every session and 2,719 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.