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/contentstack/contentstack-agent-skills/developer-hub-app-architectnpx skills add contentstack/contentstack-agent-skills --skill developer-hub-app-architectgit clone --depth 1 https://github.com/contentstack/contentstack-agent-skillsWhat 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.00000 | $0.01906 |
| Opus 5 | $0.00000 | $0.00953 |
| Sonnet 5 | $0.00000 | $0.00381 |
| Haiku 4.5 | $0.00000 | $0.00191 |
Grade A, and why
developer-hub-app-architect 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.
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
developer-hub-app-architect
Developer Hub App Architect
Description
Turn Contentstack Developer Hub and Marketplace app ideas into concrete implementations. Choose the right UI location, map the architecture, generate boilerplate-aligned React/TypeScript code, and troubleshoot setup, SDK, manifest, proxy, and publishing issues.
When to Use
Use when a user needs help designing or building a Contentstack Developer Hub or Marketplace app. Use when choosing the right UI location for a feature. Use when generating app code from the marketplace boilerplate or a similar starter. Use when explaining manifest, setup, proxy, OAuth, or publishing steps. Use when debugging app loading, SDK, iframe, route, or location issues.
User Problem
Users need to turn app ideas into working Contentstack apps without guessing at UI locations, Developer Hub setup, or SDK integration details. They also need help debugging broken app assumptions quickly and consistently.
Success Criteria
Selects the best UI location(s) with clear tradeoffs when multiple options fit. Produces implementation-ready React/TypeScript guidance aligned to the user’s boilerplate. Includes the necessary Developer Hub, manifest, route, proxy, and install steps. Avoids exposing secrets and keeps credentials server-side. Uses a repeatable troubleshooting checklist for broken apps.
Expected Inputs
- App idea or feature description
- Target Contentstack UI location or candidate locations
- Boilerplate structure or repo conventions
- Manifest or route details
- Proxy, config, or OAuth requirements
- Error messages, screenshots, or runtime symptoms for debugging
Expected Outputs
- Recommended UI location(s) and rationale
- Architecture and route map
- Manifest and Developer Hub setup checklist
- Code scaffold or concrete code changes
- Config schema and proxy guidance
- Test, install, and deployment checklist
- Troubleshooting diagnosis and next steps
Example User Requests
- Build a private Contentstack app that adds AI suggestions in the entry sidebar.
- Which UI location should I use for a product taxonomy picker?
- Generate an app configuration page and save API credentials through proxy variables.
- Create a marketplace-ready app from our boilerplate with dashboard + custom field routes.
- Why is my app loading but appSdk.location.CustomField is undefined?
- Turn this app idea into manifest config, route plan, and starter code.
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.
- 2d ago First seen · 181 lines · 0 tokens per session scan A 5df3c5d2dd31
developer-hub-app-architect is a skill published in the GitHub repository contentstack/contentstack-agent-skills (5 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,906 tokens. 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.