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 commands/julianoczkowski/create-trimble-app/remove-dev-contentgit clone --depth 1 https://github.com/julianoczkowski/create-trimble-appWhat 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.03031 |
| Opus 5 | $0.00000 | $0.01515 |
| Sonnet 5 | $0.00000 | $0.00606 |
| Haiku 4.5 | $0.00000 | $0.00303 |
Grade A, and why
remove-dev-content 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 — 395 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remove Dev Content
Remove all development and exploration content from this Modus Angular app, preparing it for production use while keeping all core Modus wrapper components intact.
Overview
This command removes:
- Dev Panel (floating development panel with toggle button)
- All 44 component demo pages
- Reference pages (colors, icons, components gallery)
- Dev-only helper components and data files
- Icon reference data (
data/modusIcons.tsandsrc/app/data/)
And updates:
- Icon names validation script to handle missing icon reference file gracefully
While preserving:
- All 48 Modus wrapper components
- Theme system (ThemeService)
- Core infrastructure (main.ts, styles.css, app.config.ts)
Step 1: Delete Entire Directories
Remove these directories completely:
src/app/demos/ # 44 component demo pages + shared/
src/app/dev/ # Dev panel infrastructure (service, component, config)
src/app/dev-pages/ # Colors, Icons, Components gallery pages
src/app/data/ # component-demos.ts, modus-icons.ts (dev-only data)
data/ # modusIcons.ts (root level, used by dev IconsPage)
Step 2: Delete Dev-Only Files from src/app/components/
Remove this file from src/app/components/:
src/app/components/theme-demo.component.ts
Keep all other files - the 48 modus-*.component.ts wrappers, index.ts, and README.md.
Step 3: Update src/app/app.ts
Remove all dev panel imports and usage. The file should become:
import { Component, OnInit, inject } from '@angular/core';
import { RouterOutlet } from '@angular/router';
import { ThemeService } from './services/theme.service';
/**
* Main Application Component.
*
* Structure:
* - Router outlet for application pages
*
* Getting Started:
* 1. Edit src/app/pages/home/home.component.ts for your landing page
* 2. Add new pages in src/app/pages/
* 3. Add routes in src/app/app.routes.ts
*/
@Component({
selector: 'app-root',
imports: [RouterOutlet],
template: `<router-outlet />`,
host: {
class: 'min-h-screen flex flex-col',
},
})
export class App implements OnInit {
private readonly themeService = inject(ThemeService);
ngOnInit(): void {
// Initialize theme service - loads theme from localStorage
this.themeService.getThemeConfig();
}
}
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 · 395 lines · 0 tokens per session scan A 8147408445ce
remove-dev-content is a command published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,031 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.