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 jaylpp/pandajay-skills --skill req-to-hours-estimategit clone --depth 1 https://github.com/jaylpp/pandajay-skillsWrote 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/jaylpp/pandajay-skills/req-to-hours-estimate)<a href="https://agentmods.dev/skills/jaylpp/pandajay-skills/req-to-hours-estimate"><img src="https://agentmods.dev/badge/skills/jaylpp/pandajay-skills/req-to-hours-estimate/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/jaylpp/pandajay-skills/req-to-hours-estimate"><img src="https://agentmods.dev/badge/skills/jaylpp/pandajay-skills/req-to-hours-estimate.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.00075 | $0.02044 |
| Opus 5 | $0.00037 | $0.01022 |
| Sonnet 5 | $0.00015 | $0.00409 |
| Haiku 4.5 | $0.00007 | $0.00204 |
Grade A, and why
req-to-hours-estimate 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 11d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
需求转工时评估报告
输入前置检查
在开始流程前，先检查用户提供的需求描述是否足够：
- 若需求描述不足 50 字或缺少核心功能点，先向用户提问：需求背景是什么？主要功能有哪些？
- 若信息充分，直接进入第一步。
工作流程
第一步：需求预处理
输入：用户提供的原始需求描述
对原始需求进行初步分析，为后续步骤准备结构化输入：
- 识别核心痛点：用户当前面临的问题、低效环节、业务瓶颈
- 挖掘潜在需求：隐含需求、扩展场景、未来可延展方向
- 风险评估：技术风险、业务风险、集成风险、数据迁移风险
- 用户故事拆解：将需求拆分为可交付的独立用户故事
输出用户故事列表（格式：作为[角色]，我希望[行为]，从而[目的]）
输出：用户故事列表 + 风险列表（传入第二步）
第二步：生成开发文档
输入：原始需求 + 第一步产出的用户故事列表
调用 skill：/req-to-dev-doc
将需求转换成结构化开发文档，包含：
- 用户故事
- 功能描述
- 影响范围（涉及模块、Entity、接口）
- 注意点/风险项
- 待确认项
- 验收标准
输出：结构化开发文档（传入第三步）
第三步：匹配资源配置
输入：第二步产出的开发文档
调用 skill：/dev-doc-match-resource
基于开发文档和员工能力资源矩阵，分析匹配资源配置：
- 产品设计人员及技能等级
- 前端开发人员及技能等级
- 后端开发人员及技能等级
- 测试人员及负责模块
- 资源风险提示
输出：资源配置建议（人员列表 + 技能等级）（传入第四步）
第四步：工时评估与报告生成
输入：开发文档（第二步）+ 资源配置（第三步）
结合对应位置的项目相关代码进行评估（位置：当前项目）：
-
搜索相关代码：
- 搜索涉及相关模块的代码文件
- 识别 Entity、Service、Controller、Mapper 等层次
- 分析现有代码复杂度和可复用性
-
工时评估维度：
维度 评估内容 需求分析 需求澄清、原型设计、方案评审 前端开发 页面开发、组件复用、交互实现 后端开发 接口开发、业务逻辑、数据处理 数据库设计 表结构设计、Liquibase脚本编写 系统集成 第三方接口对接、数据同步 测试 功能测试、集成测试、回归测试 上线部署 环境配置、数据迁移、上线验证 工时明细表列：阶段、任务、设计、前端、后端、测试、合计(人天) "需求分析"阶段的工时归入"设计"列
-
按报告模板输出完整工时评估报告
- 参照示例格式输出：
references/example-report.md
- 参照示例格式输出：
输出：完整工时评估报告（Markdown 格式）。
第五步：输出自检
报告生成后，逐项检查以下内容，发现问题立即修正后再输出给用户：
- 结构完整性：七个章节（需求概述、功能范围、技术方案、资源配置、工时评估、待确认项、报价建议）是否齐全
- 数据一致性：
- 工时明细表的合计行 = 各行之和
- 报价建议中的工时数 = 工时明细表的合计数
- 资源配置中的人员 = 工时明细表中涉及的角色
- 技能等级调整系数是否已正确应用
- 风险预留：是否按复杂度等级计入了对应比例的风险预留
评估规则
-
技能等级调整系数：
- 精通（3）：1.0
- 熟悉（2）：1.3
- 了解（1）：1.5
-
复杂度评估：
- 低：常规CRUD操作，可复用现有组件
- 中：涉及业务逻辑处理、多表关联、流程控制
- 高：涉及系统集成、复杂计算、性能优化、技术难点
-
风险预留：
- 低风险：预留10%
- 中风险：预留20%
- 高风险：预留30%
异常处理
| 异常情况 | 处理方式 |
|---|---|
/req-to-dev-doc 未触发或输出不完整 |
由本 skill 自行完成开发文档整理，继续后续步骤 |
/dev-doc-match-resource 未触发或无匹配资源 |
在报告资源配置章节注明"待确认"，使用默认等级2系数估算工时 |
| 代码库搜索无结果（新项目/新模块） | 按全新开发估算，不计复用收益，风险预留提升至30% |
| 需求描述过于简短 | 暂停流程，向用户提问补充关键信息后再继续 |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 188 lines · 75 tokens per session scan A 25bb0bbddd12
req-to-hours-estimate is a skill published in the GitHub repository jaylpp/pandajay-skills (11 stars, last pushed 3mo ago), licensed MIT. It adds 75 tokens to every session and 2,044 once invoked, about $0.0004 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-30.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.