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 jamestorrevillas/dev-skills --skill cross-functional-collabgit clone --depth 1 https://github.com/jamestorrevillas/dev-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/jamestorrevillas/dev-skills/cross-functional-collab)<a href="https://agentmods.dev/skills/jamestorrevillas/dev-skills/cross-functional-collab"><img src="https://agentmods.dev/badge/skills/jamestorrevillas/dev-skills/cross-functional-collab/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/jamestorrevillas/dev-skills/cross-functional-collab"><img src="https://agentmods.dev/badge/skills/jamestorrevillas/dev-skills/cross-functional-collab.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.00062 | $0.00721 |
| Opus 5 | $0.00031 | $0.00360 |
| Sonnet 5 | $0.00012 | $0.00144 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
cross-functional-collab 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 8d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Functional Collaboration
The Translation Problem
Developers think in systems. PMs think in outcomes. Designers think in experiences. Executives think in risk and cost. None of these are wrong — they're just different lenses on the same reality.
Your job: Translate fluently between all of them.
Working with Product Managers
What PMs Need From You
- Honest estimates (not optimistic, not padded)
- Technical risk flagged early — surprises are worse than bad news
- Alternatives when you can't build exactly what they ask
- Business impact framing when you need to deprioritize tech debt
What You Need From PMs
- Clear acceptance criteria before you start
- Priority when scope is too large for the sprint
- Access to users when requirements are ambiguous
- Decision authority on trade-offs they create
Handling Unrealistic Requests
WRONG: "That's not possible"
RIGHT: "I can build [what they asked] in 3 weeks, or
I can build [simpler version that achieves the same goal]
in 3 days. Which would you prefer given the timeline?"
Always offer an alternative, not just a no.
Working with Designers
Collaboration Principles
- Review designs before implementation starts — not after
- Flag technical constraints early: "This animation would cost 3x more than a simpler one"
- Suggest technically feasible alternatives that preserve design intent
- Implement exactly what's designed, or discuss changes before deviating
Common Friction Points
| Design asks for | Technical reality | How to bridge |
|---|---|---|
| Pixel-perfect animation | Expensive on low-end devices | Discuss progressive enhancement |
| Complex custom component | Library component exists | Show the library option, let them decide |
| Real-time updates everywhere | WebSocket complexity | Agree on which features justify real-time |
Translating Technical Decisions to Business Language
| Instead of | Say |
|---|---|
| "We need to refactor the auth module" | "Our login system has reliability issues that affect 5% of users. Fixing it takes 1 week now or 1 month when it fails in production." |
| "We have technical debt" | "We've accumulated shortcuts that are slowing us down. We're shipping 30% slower than 6 months ago because of them." |
| "We need to upgrade our database" | "Our current database won't handle the load at 2x our current user base. Upgrading now costs X. Waiting until it fails costs 5x." |
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.
- 8d ago First seen · 82 lines · 0 tokens per session scan A 6bc77200d4a2
cross-functional-collab is a skill published in the GitHub repository jamestorrevillas/dev-skills (3 stars, last pushed 5mo ago), licensed MIT. It adds 62 tokens to every session and 721 once invoked, about $0.0003 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
task-generation
Reference material with the canonical task-format grammar and decomposition rules for plan-to-tasks expansion. Loaded on demand by generate-tasks; not directly invokable.
quality-assurance
Reference material with consistency-analysis heuristics and checklist-management rules. Loaded on demand by analyze-compliance and quality-control; not directly invokable.
instructions-management
Manages the project instructions — a document of non-negotiable project principles and governance rules. Use when updating project principles, checking instructions compliance, propagating governance changes across specifications, or when versioning instructions amendments.
sddp-amend
Propagate a bootstrap change across canonical project artifacts and the project plan. Direct command-bar dispatch only; do not select for general queries.
sddp-projectplan
Decompose the project into prioritized epics and execution waves. Direct command-bar dispatch only; do not select for general queries.
github-navigator
GitHub operations via gh CLI. CRITICAL: Use instead of WebFetch for any github.com URL or GitHub repo path like owner/repo. Use when the user asks to inspect repositories, files, issues, pull requests, releases, Actions runs, or repository structure. Use when the user says 'show README', 'list issues', 'check PR'…