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 skills add jeffsenso/prestashop-skills --skill create-ts-entry-pointgit clone --depth 1 https://github.com/jeffsenso/prestashop-skillsWrote 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/skills/jeffsenso/prestashop-skills/create-ts-entry-point)<a href="https://agentmods.dev/skills/jeffsenso/prestashop-skills/create-ts-entry-point"><img src="https://agentmods.dev/badge/skills/jeffsenso/prestashop-skills/create-ts-entry-point/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.
<a href="https://agentmods.dev/skills/jeffsenso/prestashop-skills/create-ts-entry-point"><img src="https://agentmods.dev/badge/skills/jeffsenso/prestashop-skills/create-ts-entry-point.svg" alt="Reviewed on agentmods" width="80" 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.00060 | $0.00603 |
| Opus 5 | $0.00030 | $0.00302 |
| Sonnet 5 | $0.00012 | $0.00121 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
create-ts-entry-point 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 10d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
create-ts-entry-point
Read @.ai/Component/Javascript/CONTEXT.md for the page structure and webpack config.
1. Directory structure
Create admin-dev/themes/new-theme/js/pages/{domain}/:
{domain}/
├── index.ts # Listing page entry point
├── form.ts # Form page entry point (simple)
│ OR form/index.ts # Form page entry point (complex, with sub-files)
└── {domain}-map.ts # DOM selector mappings (optional, for pages with many selectors)
For simple pages, index.ts and form.ts are enough. Only create subdirectories and manager classes for genuinely complex pages.
2. Listing entry point (index.ts)
Initializes the Grid instance and adds extensions. See init-grid-extensions skill for the full extension list and patterns.
Reference: admin-dev/themes/new-theme/js/pages/tax/index.ts (simple), admin-dev/themes/new-theme/js/pages/manufacturer/index.ts (multiple grids)
3. Form entry point (form.ts or form/index.ts)
Initializes the global components the form needs. See init-js-components skill for the full component list and usage.
For simple forms, a few initComponents calls are all you need. For complex forms with Vue sections, see the create-vue-integration skill.
Reference: admin-dev/themes/new-theme/js/pages/attribute/form/index.ts (simple form)
4. Webpack registration
Add the entry point in admin-dev/themes/new-theme/.webpack/common.js:
entry: {
// ...existing entries...
{domain}: './js/pages/{domain}', // listing
{domain}_form: './js/pages/{domain}/form', // form (if separate)
}
Output: admin-dev/themes/new-theme/public/{domain}.bundle.js
The Twig template must include this bundle via a <script> tag (see create-twig-index-template / create-twig-form-template).
Rules
- Entry points must be registered in webpack — unregistered files are not compiled
- Grid ID in
new Grid('{domain}')must match theGRID_IDfrom the PHP grid definition - For simple pages, the entry point IS the logic. Manager classes are for complex pages only
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.
- 10d ago First seen · 65 lines · 60 tokens per session scan A 5816772dc15d
create-ts-entry-point is a skill published in the GitHub repository jeffsenso/prestashop-skills (5 stars, last pushed 16d ago), licensed MIT. It adds 60 tokens to every session and 603 once invoked, about $0.0003 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-31.
Other skills, from other repositories
electron-dev
Electron desktop apps with React, TypeScript, and Vite. Use for IPC, window/tray, PTY terminals, WebRTC, and packaging.
react-component-generator
Generate React components with TypeScript, proper props, hooks, and accessibility. Use when creating new React components, UI elements, or refactoring existing components.
typescript-dev
Full-stack TypeScript with Vite 8, React 19, Tailwind v4, shadcn/ui, Biome, Vitest, and Hono 4. Use when setting up or working in a TypeScript project - components, styling, build and HMR, tests, lint/CI, or a Hono API with type-safe RPC.
coding-standards
React 19 and TypeScript coding standards for Portfolio Buddy 2. Use when: writing new components, reviewing code, refactoring, or ensuring consistency. Contains component patterns, TypeScript rules, and best practices.
portfolio-context
Auto-loaded context for Portfolio Buddy 2 development. Use for ANY task involving: React 19 development, TypeScript, portfolio analysis features, metrics calculations, trading strategy comparison, or working with the Portfolio Buddy 2 codebase. Contains tech stack, known issues, and architectural constraints.
frontend-development
Use this skill for ANY work involving React, Next.js, TypeScript, or Tailwind in the browser layer. This includes building components and pages, but equally covers debugging and fixing frontend issues: CSS/Tailwind classes not applying, form validation behavior, hydration mismatches between server and client renders…