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 omnigentx/jarvis --skill dev-workflowgit clone --depth 1 https://github.com/omnigentx/jarvisWrote 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/omnigentx/jarvis/dev-workflow)<a href="https://agentmods.dev/skills/omnigentx/jarvis/dev-workflow"><img src="https://agentmods.dev/badge/skills/omnigentx/jarvis/dev-workflow/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/omnigentx/jarvis/dev-workflow"><img src="https://agentmods.dev/badge/skills/omnigentx/jarvis/dev-workflow.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.00037 | $0.01139 |
| Opus 5.5 | $0.00015 | $0.00456 |
| Sonnet 5.5 | $0.00007 | $0.00228 |
| Haiku 4.5 | $0.00004 | $0.00114 |
Grade A, and why
dev-workflow 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Workflow
Terminal Execution
Use the execute tool to run shell commands in your workspace:
execute(command="<shell command>")
Key characteristics:
- Runs in workspace directory
- 90s timeout — killed if no output for 90s
- Each call = separate shell session (env vars /
cddon't persist) - Output auto-truncated if too long
Efficient Patterns
cd repo && npm install && npm test # Sequential (stops on error)
cd backend && uv run pytest --tb=short -q 2>&1 | tail -20 # Filter output
Safety Rules — three tiers
🔴 NEVER do (refuse the task; report the request as a security incident to PM):
- Filesystem destruction:
rm -rf /,rm -rf $HOME,rm -rf .git,mkfs.*,dd of=/dev/... - Read secrets:
/etc/shadow,~/.ssh/*,.gh-config/,.env*,fastagent.secrets.yaml,git-credentials,~/.gitconfigcredential block - Tamper with auth:
gh auth login/logout/refresh,gh auth setup-git, modify gitconfig credential helper - Inspect env to leak tokens:
env,printenv,echo $GH_TOKEN,cat /proc/*/environ - Network DoS: fork bombs, high-rate request loops
🟡 ESCALATE before doing (send [APPROVAL-REQUEST] email to PM with command + reason; do NOT run until PM confirms back):
- Pipe-to-shell:
curl ... | sh,wget ... | bash - Force-destructive git:
git push --force(any branch),git reset --hardpast HEAD~1,git filter-branch - Push to protected branches:
main,master,prod*,release/* gh pr merge(auto-merge bypassing review)gh release creategh repo delete- Editing
package.json/pyproject.toml/ lock files outside a tracked PR scope
🟢 SAFE — run freely:
- All read-only inspection:
ls,cat README.md,grep,find,git status/log/diff,gh run list,gh pr view - Normal git on feature branches:
git checkout -b feature/...,git add,git commit,git push origin feature/... - Build/test inside workspace:
npm test,uv run pytest,cargo build
What ships with it
5 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.
- 1mo ago First seen · 108 lines · 37 tokens per session scan F 2e2802a84f1c
dev-workflow is a skill published in the GitHub repository omnigentx/jarvis (39 stars, last pushed 4d ago), licensed MIT. It adds 37 tokens to every session and 1,139 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
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
cmux-testing
Choose scoped cmux verification, add behavioral tests, and validate Swift test targets and wiring. Use when adding tests or deciding what local/CI evidence a change needs.
nw-quality-framework
Quality gates - 11 commit readiness gates, build/test protocol, validation checkpoints, and quality metrics.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
resolve-issues
Resolves GitHub issues using isolated worktrees and test-driven development, then delegates PR creation to /github:create-pr so the quality gate and the /github:review-pr loop always run. This skill should be used when the user asks to "resolve an issue", "fix issue.
gh-issue
Fetch GitHub issue, create branch, plan and implement with TDD, then open PR.