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/bdiasti/maestro-bundle-cli/responsive-layoutnpx skills add bdiasti/maestro-bundle-cli --skill responsive-layoutgit clone --depth 1 https://github.com/bdiasti/maestro-bundle-cliWhat 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.00040 | $0.01787 |
| Opus 5 | $0.00020 | $0.00894 |
| Sonnet 5 | $0.00008 | $0.00357 |
| Haiku 4.5 | $0.00004 | $0.00179 |
Grade A, and why
responsive-layout 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Responsive Layout
Build mobile-first responsive layouts using Tailwind CSS with sidebar navigation, dashboard grids, and adaptive content areas.
When to Use
- User needs to create a page layout with sidebar and header
- User wants to build a responsive dashboard with metric cards
- User needs a mobile-first grid that adapts to screen sizes
- User wants to add responsive navigation (sidebar + mobile menu)
- User needs to structure a page with proper spacing and overflow handling
Available Operations
- Create a full app layout (sidebar + header + main content)
- Build responsive dashboard grids with metric cards
- Implement collapsible sidebar with mobile drawer
- Set up responsive content grids
- Add proper scroll areas and overflow handling
Multi-Step Workflow
Step 1: Install Dependencies
npm install clsx tailwind-merge lucide-react
Verify Tailwind is configured:
npx tailwindcss --help
# If not installed: npm install -D tailwindcss postcss autoprefixer && npx tailwindcss init -p
Step 2: Create the App Shell Layout
// src/layouts/AppLayout.tsx
import { useAppStore } from '@/stores/useAppStore';
export function AppLayout({ children }: { children: React.ReactNode }) {
const sidebarOpen = useAppStore((s) => s.sidebarOpen);
return (
<div className="flex h-screen bg-gray-50">
{/* Sidebar */}
<Sidebar open={sidebarOpen} />
{/* Main area */}
<div className="flex-1 flex flex-col overflow-hidden">
<Header />
<main className="flex-1 overflow-y-auto p-4 md:p-6 lg:p-8">
{children}
</main>
</div>
</div>
);
}
Step 3: Build the Sidebar
// src/components/Sidebar.tsx
import { NavLink } from 'react-router-dom';
import { Home, List, Users, Settings, X } from 'lucide-react';
import { useAppStore } from '@/stores/useAppStore';
const navItems = [
{ to: '/dashboard', label: 'Dashboard', icon: Home },
{ to: '/items', label: 'Items', icon: List },
{ to: '/team', label: 'Team', icon: Users },
{ to: '/settings', label: 'Settings', icon: Settings },
];
export function Sidebar({ open }: { open: boolean }) {
const toggleSidebar = useAppStore((s) => s.toggleSidebar);
return (
<>
{/* Mobile overlay */}
{open && (
<div className="fixed inset-0 bg-black/50 z-40 lg:hidden" onClick={toggleSidebar} />
)}
{/* Sidebar */}
<aside
className={cn(
'fixed lg:static inset-y-0 left-0 z-50 w-64 bg-white border-r transform transition-transform lg:translate-x-0',
open ? 'translate-x-0' : '-translate-x-full'
)}
>
<div className="flex items-center justify-between p-4 border-b">
<h1 className="text-xl font-bold">App Name</h1>
<button onClick={toggleSidebar} className="lg:hidden">
<X className="w-5 h-5" />
</button>
</div>
<nav className="p-4 space-y-1">
{navItems.map((item) => (
<NavLink
key={item.to}
to={item.to}
className={({ isActive }) =>
cn('flex items-center gap-3 px-3 py-2 rounded-lg text-sm',
isActive ? 'bg-blue-50 text-blue-700 font-medium' : 'text-gray-600 hover:bg-gray-100'
)
}
>
<item.icon className="w-5 h-5" />
{item.label}
</NavLink>
))}
</nav>
</aside>
</>
);
}
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 · 206 lines · 40 tokens per session scan A 1fb6b04ddb26
responsive-layout is a skill published in the GitHub repository bdiasti/maestro-bundle-cli (21 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 1,787 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-30.
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.