What is cross-tech-stack-spec-skill?

An extension for documenting projects that span frontend, mobile, Python, or other technology layers. It adapts backend-oriented mapping so it can follow connections between pages, apps, clients, servers, tasks, bridges, and callbacks.

Use it for cross-stack repository mapping, frontend or mobile analysis, Python projects, and routes involving pages, clients, backends, scheduled tasks, callbacks, bridges, or similar layers.

It fills gaps left by backend-only analysis when a feature crosses several kinds of code. It keeps evidence boundaries clear while following those cross-layer connections.

cross-tech-stack-spec-skill — Skill by SYZ-Coder

Install

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.

agentmods

npx agentmods add skills/syz-coder/codebase-knowledge-wiki/cross-tech-stack-spec-skill

Any agent

npx skills add SYZ-Coder/codebase-knowledge-wiki --skill cross-tech-stack-spec-skill

Clone the repo

git clone --depth 1 https://github.com/SYZ-Coder/codebase-knowledge-wiki

Made for: Claude Code, Codex.

Per session 112 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,757 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00112	$0.01757
Opus 5	$0.00056	$0.00879
Sonnet 5	$0.00022	$0.00351
Haiku 4.5	$0.00011	$0.00176

Measured 2d ago against content hash 266b8fcc6aed, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cross-tech-stack-spec-skill 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 2d 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.

cross-tech-stack-spec-skill/SKILL.md · 154 lines

How it starts

The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cross Tech Stack Spec Skill

Overview

Use this skill as an explicit extension layer for projects that are not well served by backend-service language alone. It is designed for mobile projects, H5/web frontend projects, Python projects, and mixed-stack repositories that need cross-layer mapping.

Activation Boundary

Use this skill only when one of these is true:

the user explicitly says to enable cross-tech-stack expansion
the target repository is primarily mobile, H5/web frontend, Python, or mixed-stack
the user wants cross-layer mapping across page/app/client/backend/task/callback/bridge boundaries

Do not use this skill by default for ordinary backend microservice analysis. In those cases, continue using the backend-service-spec-skill.

Core Purpose

This skill adds eight kinds of adaptation:

rename backend-oriented analysis concepts into stack-neutral concepts
adapt project mapping for mobile / H5 / Python repository shapes
adapt router-map thinking for cross-layer routes instead of only service-to-service routes
preserve strict evidence boundaries when crossing frontend, client, backend, task, bridge, and callback layers
reduce low-signal scan noise in large mixed workspaces
make caller-to-handler interface mapping easier in mixed-stack repositories
upgrade domain pages from backend-only service structure to mixed-stack context structure when needed
support incremental updates for long-term knowledge maintenance

Default Working Rules

When this skill is active:

keep the original four function ideas: create_codemap, build_domain_map, crate_router_map, service_deep_dive
reinterpret them in a stack-neutral way
prefer project/module/page/task/component/bridge wording over backend-only service wording when the codebase requires it
treat cross-layer diagrams as first-class outputs, using Markdown + Mermaid instead of image-only artifacts
keep fact/clue discipline exactly as strict as in the existing backend-service-spec-skill workflow

Read the full file on GitHub · 154 lines

Files

What ships with it

45 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.

Changes

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.

2d ago First seen · 154 lines · 112 tokens per session scan A 266b8fcc6aed

Subscribe to this mod's changes

cross-tech-stack-spec-skill is a skill published in the GitHub repository SYZ-Coder/codebase-knowledge-wiki (9 stars, last pushed 2mo ago), licensed MIT. It adds 112 tokens to every session and 1,757 once invoked, about $0.0006 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.

Backend and APIs Frontend Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 170 tokens