agentmods.dev

cross-tech-stack-spec-skill

cross-tech-stack-spec-skill is a skill for Codex from SYZ-Coder/codebase-knowledge-wiki. It costs 112 tokens per session (1,757 once invoked), scanned A, original, MIT.

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.

In plain words
What is it for?
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.
Why use it?
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.

Skill for Codex

Written for Codex: agents/openai.yaml present.

not rated 9repo 4mo ago A scan 112 tokens original MIT

Good fit 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.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/syz-coder/codebase-knowledge-wiki/cross-tech-stack-spec-skill
View source ↗ SYZ-Coder/codebase-knowledge-wiki
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.

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: Codex.

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

agentmods badge for cross-tech-stack-spec-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/syz-coder/codebase-knowledge-wiki/cross-tech-stack-spec-skill/github.svg)](https://agentmods.dev/skills/syz-coder/codebase-knowledge-wiki/cross-tech-stack-spec-skill)
Your own site
<a href="https://agentmods.dev/skills/syz-coder/codebase-knowledge-wiki/cross-tech-stack-spec-skill"><img src="https://agentmods.dev/badge/skills/syz-coder/codebase-knowledge-wiki/cross-tech-stack-spec-skill/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.

agentmods 80×15 button for cross-tech-stack-spec-skill

Your own site · 80×15
<a href="https://agentmods.dev/skills/syz-coder/codebase-knowledge-wiki/cross-tech-stack-spec-skill"><img src="https://agentmods.dev/badge/skills/syz-coder/codebase-knowledge-wiki/cross-tech-stack-spec-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00112 $0.01757
Opus 5.5 $0.00045 $0.00703
Sonnet 5.5 $0.00022 $0.00351
Haiku 4.5 $0.00011 $0.00176

Measured 1mo ago against content hash 266b8fcc6aed, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

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:

  1. rename backend-oriented analysis concepts into stack-neutral concepts
  2. adapt project mapping for mobile / H5 / Python repository shapes
  3. adapt router-map thinking for cross-layer routes instead of only service-to-service routes
  4. preserve strict evidence boundaries when crossing frontend, client, backend, task, bridge, and callback layers
  5. reduce low-signal scan noise in large mixed workspaces
  6. make caller-to-handler interface mapping easier in mixed-stack repositories
  7. upgrade domain pages from backend-only service structure to mixed-stack context structure when needed
  8. 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.

  1. 1mo 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 4mo ago), licensed MIT. It adds 112 tokens to every session and 1,757 once invoked, about $0.0004 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-31.

Writing and docs
Related

Other skills, from other repositories

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…

microsoft/ai-agents-for-beginners · 200 tokens

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

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.

microsoft/vscode · 53 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

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens