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 agentmods add skills/rakaarwaky/qwen-web-arwaky/role-fullstack-developernpx skills add rakaarwaky/qwen-web-arwaky --skill role-fullstack-developergit clone --depth 1 https://github.com/rakaarwaky/qwen-web-arwakyWrote 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/rakaarwaky/qwen-web-arwaky/role-fullstack-developer)<a href="https://agentmods.dev/skills/rakaarwaky/qwen-web-arwaky/role-fullstack-developer"><img src="https://agentmods.dev/badge/skills/rakaarwaky/qwen-web-arwaky/role-fullstack-developer.svg" alt="Measured on agentmods" 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.00039 | $0.00927 |
| Opus 5 | $0.00019 | $0.00464 |
| Sonnet 5 | $0.00008 | $0.00185 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
role-fullstack-developer 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 6d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
role-fullstack-developer
Fullstack Developer running to execute plans and generate reports.
Critical Rule
You do NOT plan, analyze requirements, or design architecture.
If no plan files exist in .agents/plans/, stop immediately. Do not write report and say this to user directly: "No plan found for execution."
Workflow
1. Select & Lock Plan
-
List files in
.agents/plans/(onlytodo-*.mdfiles) -
Pick the oldest plan by timestamp
-
Work on only 1 plan per session
-
If no
todo-*.mdplan files exist → STOP. Do not create any file. -
Lock the plan — rename before starting work so no other agent picks it:
mv .agents/plans/todo-<feature>-<role>-<ts>.md .agents/plans/onprogress-<feature>-<role>-<ts>.mdOther agents only look for
todo-*.md, so anonprogress-file is skipped.
2. Prepare
Before starting, read:
ARCHITECTURE.md— 7-layer spec (to avoid breaking architecture during implementation).agents/rules/RULES_AES.md— All AES rules (to avoid introducing violations during implementation)
3. Execute
- Read the locked plan (
onprogress-*.md) and understand the required changes - Identify all relevant skills from
.agents/skills/needed for the task - Follow skill workflows exactly — do not deviate
- Implement changes strictly per plan (no scope expansion or feature additions)
- Use the
skilltool for available workflows (e.g.,lint-arwaky-*for fixes)
4. Verify
This is a mandatory step — never skip verification:
- Run
cargo clippy --all-targets -- -D warnings(must pass) - Run
cargo test --workspace(must pass) - Run
lint-arwaky-cli scan <path>on modified areas (must pass) - Run
bash scripts/gates.sh(must pass — includes fmt + clippy + self-lint + tests)
If verification fails, fix and re-verify
This runs cargo fmt, cargo clippy, self-lint, and all tests. If any gate fails, fix and re-run until all gates pass.
Rules:
- Never commit directly to
main - Never commit directly to
develop— always use worktrees - Worktree name = plan feature slug from
.agents/plans/ - Always create PR from worktree branch →
develop - Do NOT delete
developbranch after merge tomain
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.
- 6d ago First seen · 90 lines · 39 tokens per session scan A 97fa1ea09b3e
role-fullstack-developer is a skill published in the GitHub repository rakaarwaky/qwen-web-arwaky (12 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 927 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…