Borrowing it
Nothing to install: this file belongs to MontoyaAndres/ganju. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MontoyaAndres/ganju/main/.claude/commands/web-component.mdgit clone --depth 1 https://github.com/MontoyaAndres/ganjuWrote 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/commands/montoyaandres/ganju/web-component)<a href="https://agentmods.dev/commands/montoyaandres/ganju/web-component"><img src="https://agentmods.dev/badge/commands/montoyaandres/ganju/web-component.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.00000 | $0.01087 |
| Opus 5 | $0.00000 | $0.00544 |
| Sonnet 5 | $0.00000 | $0.00217 |
| Haiku 4.5 | $0.00000 | $0.00109 |
Grade A, and why
web-component 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a new web component following the established project conventions.
Input
$ARGUMENTS
Project Architecture
This is a monorepo (npm workspaces + Turbo) with three key packages:
packages/ui/— Reusable UI components wrapping Material UI with Emotion stylingpackages/utils/— Shared utilities (Zod schemas, fetcher, constants)apps/web/— Next.js app consuming both packages
Styling System
Emotion CSS-in-JS (NOT Tailwind). Every styled component uses @emotion/styled + @emotion/react.
Theme tokens available via ({ theme }) => css:
- Colors:
theme.colors.transparent,.black,.bastille(#1C1825),.white,.red,.alto,.fernGreen,.saltBox - Fonts:
theme.fonts.xs(12px) throughtheme.fonts['9xl'](100px) - Shadows:
theme['custom-shadows'].smallest,.small - Breakpoints:
theme.screens.sm(640px),.md(768px),.lg(1024px),.xl(1280px),.['2xl'](1536px) - Font family: Fustat (set globally)
Responsive design is mobile-first: base styles for mobile, @media (min-width: ${theme.screens.md}) for larger screens.
File Structure Conventions
For packages/ui components (reusable across apps):
packages/ui/src/components/<component-name>/
index.tsx — Component logic, wraps Material UI, uses Wrapper from styles
styles.tsx — Emotion styled components with theme access
styles.tsx pattern:
import { css } from '@emotion/react';
import styled from '@emotion/styled';
interface IProps {
// Component-specific style props
}
export const Wrapper = styled.div<IProps>`
${({ theme }) => css`
// Styles using theme tokens
`}
`;
index.tsx pattern:
import { ReactNode } from 'react';
import { Wrapper } from './styles';
export interface IProps {
children: ReactNode;
}
export const ComponentName = (props: IProps) => {
const { children, ...rest } = props;
return <Wrapper>{children}</Wrapper>;
};
After creating, register in packages/ui/src/components/index.tsx:
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 · 131 lines · 0 tokens per session scan A a018644f064f
web-component is a command published in the GitHub repository MontoyaAndres/ganju (2 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,087 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 commands, from other repositories
extract
Extract HTML from a Storybook component.
add-tool
Build a new UEFN Toolbelt tool named "$ARGUMENTS". Follow the tool-developer agent workflow exactly.
deploy
Generate the exact deploy + test sequence for the current change.
publish-check
Run a full pre-publish audit. Check everything before the user submits their island to Fortnite.
mx-page-clone-from-template
GATED WRITE. Clone a Mendix page to a new name + optional entity rebinding via the mxcli MDL round-trip. Routes through the shadow-write engine (7 safety pillars). Pre-classifies the source as SIMPLE / COMPLEX / UNCLONEABLE; refuses UNCLONEABLE, requires --allow-lossy on COMPLEX. Auto-emits a /mx-handoff sheet for…
checklist
Generate a custom checklist for the current feature based on user requirements.