Borrowing it
Nothing to install: this file belongs to usk6666/yorishiro-proxy. 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/usk6666/yorishiro-proxy/main/.claude/skills/project/SKILL.mdgit clone --depth 1 https://github.com/usk6666/yorishiro-proxyWrote 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/usk6666/yorishiro-proxy/project)<a href="https://agentmods.dev/skills/usk6666/yorishiro-proxy/project"><img src="https://agentmods.dev/badge/skills/usk6666/yorishiro-proxy/project/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/usk6666/yorishiro-proxy/project"><img src="https://agentmods.dev/badge/skills/usk6666/yorishiro-proxy/project.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.00015 | $0.02181 |
| Opus 5.5 | $0.00006 | $0.00872 |
| Sonnet 5.5 | $0.00003 | $0.00436 |
| Haiku 4.5 | $0.00002 | $0.00218 |
Grade A, and why
project 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 1mo 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/project
A skill that handles the planning and tracking sides of the "plan → implement → track" development cycle. Provides milestone progress overview, Issue creation from the roadmap, and post-implementation document sync.
Fixed Parameters
- Team: Usk6666
- Project: yorishiro-proxy
- Roadmap doc ID: d413edd7-d296-433a-ab94-11d4dd57d883
Subcommands
/project status— Overview of milestone progress/project plan <milestone>— Gap analysis between roadmap and Linear Issues, with Issue creation. If the roadmap has no Issue table for the target milestone (greenfield), run the milestone-planner agent to derive Issues from the milestone description + spec — see "Greenfield Mode" below./project sync— Update roadmap documents after implementation is complete
/project status
The entry point for checking milestone progress and deciding what to work on next.
Steps
- Fetch all milestone progress with
mcp__linear-server__list_milestones(project=yorishiro-proxy) - Fetch the following in parallel:
mcp__linear-server__list_issues(team=Usk6666, project=yorishiro-proxy, state=started)mcp__linear-server__list_issues(team=Usk6666, project=yorishiro-proxy, state=backlog)mcp__linear-server__list_issues(team=Usk6666, project=yorishiro-proxy, state=unstarted)
- Group Issues by
projectMilestonefield - Report the following:
Output Format
## Project Progress
### Milestone Progress
| Milestone | Progress | Remaining Issues | Status |
|-----------|----------|-----------------|--------|
| M1: Foundation | 100% | — | Complete |
| M2: MCP Interface v2 | 79% | 3 issues | ← ACTIVE |
| M3: Active Testing | 0% | N issues | Not started |
| M4: Multi-Protocol | 0% | N issues | Not started |
| M5: Production Ready | 0% | N issues | Not started |
### Active: M2 — MCP Interface v2
| ID | Title | Status | Priority |
|----|-------|--------|----------|
| USK-79 | ... | Backlog | High |
| USK-80 | ... | Todo | Normal |
| ...
### Blockers
- M3 depends on M2 completion (currently 79%)
### Recommended Actions
- `/orchestrate milestone M2` to implement remaining 3 Issues
- Or `/project plan M3` to prepare M3 Issues in advance
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.
- 1mo ago First seen · 216 lines · 15 tokens per session scan A f3630aa3983a
project is a skill published in the GitHub repository usk6666/yorishiro-proxy (19 stars, last pushed yesterday), licensed Apache-2.0. It adds 15 tokens to every session and 2,181 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
daily-briefing
Start your day with a prioritized CRM briefing — works for any monday CRM setup: pipeline, contacts, accounts, leads, or no board at all. Use when someone says 'morning briefing', 'daily brief', 'what's on my plate today', 'catch me up on my deals', 'what needs attention', 'what needs my attention', 'anything urgent…
meeting-to-deal
Turn meeting transcripts into deal updates — key points, commitments, and next steps posted to matching CRM deals automatically. Auto-creates contacts for new attendees. Use when someone says "log my meetings to deals", "update CRM from calls", "what did I commit to in meetings", "sync notetaker", "log this meeting"…
Technical Debt Tracking with PMAT
Tracks and manages technical debt using PMAT (Pragmatic AI Labs MCP Agent Toolkit). Use this skill when: User asks about technical debt, TODO comments, or code quality issues Planning sprint work and need to prioritize debt repayment Conducting code audits or technical debt assessments Tracking debt accumulation…
getting-started
Connect Taskade and show the user what they can do with it. Use when the user says "set up Taskade", "connect Taskade", "what can you do in Taskade", "what is in my Taskade workspace", or when a Taskade tool fails with a sign-in or plan error.
continue-project
Find the user's saved Glif project, show its media, and add new work to it without starting a separate project. Use when: "show my recent Glif projects", "open my last image", "keep going on that one", "make 5 variations to A/B test", "same but vertical", "make a version for TikTok", "resize it to every format", "same…
build-flow
Create or change a Keboola flow that runs extractors, transformations and writers in order, optionally on a schedule. Use when the user wants to orchestrate, chain or schedule existing Keboola configurations.