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 aidi1723/safe-agent-skills --skill code-senior-fullstack-reviewgit clone --depth 1 https://github.com/aidi1723/safe-agent-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/aidi1723/safe-agent-skills/code-senior-fullstack-review)<a href="https://agentmods.dev/skills/aidi1723/safe-agent-skills/code-senior-fullstack-review"><img src="https://agentmods.dev/badge/skills/aidi1723/safe-agent-skills/code-senior-fullstack-review.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.00033 | $0.00354 |
| Opus 5 | $0.00016 | $0.00177 |
| Sonnet 5 | $0.00007 | $0.00071 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
code-senior-fullstack-review 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 7d 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.
What it actually says
Senior Fullstack Review
When To Use
Use this draft when reviewing the senior-fullstack metadata-only
candidate from claude-skills before deciding whether to author a local
OneCode skill, merge it into an existing skill, or keep it reference-only.
Safe Workflow
- Identify the task, audience, owner, source domain, target catalog category, and expected artifact.
- Compare the candidate with existing trusted Safe-Agent-Skills to avoid duplicate or overlapping guidance.
- Draft local OneCode guidance from project requirements and operator review; do not copy upstream skill bodies.
- Check provenance, license notes, runtime permissions, and connector assumptions before import.
- Produce an adoption recommendation only; Do not execute upstream content or mark this draft trusted.
Expected Output
- metadata-only candidate summary
- overlap and merge recommendation
- local authoring notes
- required verifier checklist
- adoption decision: convert, merge, keep reference-only, or reject
Verifier Expectations
- metadata-only boundary check
- duplicate skill check
- provenance and license check
- import, serial approval, schema-check, maintain-check, and verify before trust
Draft Metadata
- upstream candidate:
senior-fullstack - source domain:
engineering-team - source path:
engineering-team/skills/senior-fullstack - mapped category:
code - score:
51 - priority:
P3 - adoption before draft:
reference_only
What ships with it
1 file 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.
- 7d ago First seen · 51 lines · 33 tokens per session scan A 23c9afc4d7da
code-senior-fullstack-review is a skill published in the GitHub repository aidi1723/safe-agent-skills (2 stars, last pushed 15d ago), licensed Apache-2.0. It adds 33 tokens to every session and 354 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-31.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…