sankhya-js

A frontend screen pattern for Sankhya Addon Studio, using HTML, CSS, and AngularJS 1.x—a JavaScript framework for browser interfaces. It defines where an add-on's screen files, templates, assets, and menu registration belong.

In plain words
What is it for?
Use it to create, review, or change an add-on's HTML5 screens, including their layout, browser logic, pop-ups, styling, translations, images, and menu entries.
Why use it?
It removes the guesswork of organising custom browser screens and connecting them to the Sankhya platform. It also helps distinguish screens from add-on code that only writes directly to a database table.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/snk-devcenter/addon-studio/sankhya-js
Any agent
npx skills add snk-devcenter/addon-studio --skill sankhya-js
Clone the repo
git clone --depth 1 https://github.com/snk-devcenter/addon-studio

Made for: Claude Code, Codex.

Per session 428 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,611 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00428 $0.03611
Opus 5 $0.00214 $0.01806
Sonnet 5 $0.00086 $0.00722
Haiku 4.5 $0.00043 $0.00361

Measured 2d ago against content hash 80035d94ca9c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sankhya-js 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.

The scan reads SKILL.md. This mod also ships 7 executable files (templates/component-directive.js, templates/dataset-standalone.js, templates/filter-panel-interceptor.js, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/addon-studio/skills/sankhya-js/SKILL.md · 207 lines

How it starts

The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Telas HTML5 do addon (sankhya-js) — Addon Studio 2.0

Framework frontend proprietário do produto Sankhya, baseado em AngularJS 1.x (não Angular 2+). O addon consome o framework: a plataforma serve o bundle snk e a tela do addon declara ['snk'] como dependência. Nada do framework é buildado ou versionado dentro do addon.


Onde a tela vive

Telas ficam no módulo web do addon (<addon>-vc, plugin Gradle war):

<addon>-vc/src/main/webapp/
  html5/<Tela>/
    <Tela>.html                  # fragmento: raiz e <sk-application>, sem <html>/<head>
    <Tela>.js                    # angular.module('<Tela>App', ['snk'])
    <Tela>.css
    launcher/<Tela>.body         # <script> extras (popups, código comum)
    launcher/<Tela>.include      # <link rel="stylesheet">
    popup/<algo>.tpl.html        # templates de popup/diretiva
    popup/<algo>.controller.js
  assets/                        # ícones e imagens da tela e do menu
datadictionary/MENU_<id>.xml     # <ui url="/$ctx/<Tela>.xhtml5"> registra a tela

Scaffold oficial: gradle gerarTela -Ptela=<Tela> (task do plugin Gradle do Studio). Com -Pinstancia=<Instance> gera a variante dynaform já ligada a uma <instance> do dicionário. Detalhes, arquivos gerados e registro no menu: references/addon-screen.md.


Regras não-negociáveis

  1. AngularJS 1.xangular.module(...), $scope, $q, $http, DI por array. Nada de Angular 2+ (standalone components, signals, RxJS), nada de React.
  2. Cada tela declara o próprio módulo: angular.module('<Tela>App', ['snk']). Nunca registrar controller/service dentro de snk, snk.core.*, snk.components.* ou snk.commons — esses módulos são do framework, não do addon.
  3. DI por array (['$scope', 'ServiceProxy', function ($scope, ServiceProxy) {...}]), como no template do gerarTela. DI implícita por nome de parâmetro quebra em qualquer minificação.
  4. Backend só via ServiceProxy, com prefixo do addon no serviceName: '<addon>@<Nome>SP.<metodo>'. Sem prefixo o framework assume defModule = "mge" e chama o serviço nativo errado. Nunca montar /mge/service.sbr na mão.
  5. <Nome>SP é o serviceName do @Controller do addon — o contrato dos dois lados anda junto (skill controller).
  6. sk-entity-name casa com o name da <instance> declarada no dicionário de dados (skill data-dictionary), não com o nome da tabela nem com o da entidade Java.
  7. Arquivos do webapp em UTF-8.js, .html, .css, .body, .include. A regra ISO-8859-1 do addon vale para .java/.xml/.kt/.properties (inclusive o XML de menu que registra a tela), não para o conteúdo do webapp.
  8. Sem emoji. Texto de UI em PT-BR direto ou via SkI18nService quando a tela precisar de mais de um idioma.

Read the full file on GitHub · 207 lines

Changes

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.

  1. 2d ago First seen · 207 lines · 0 tokens per session scan A 80035d94ca9c

Subscribe to this mod's changes

sankhya-js is a skill published in the GitHub repository snk-devcenter/addon-studio (5 stars, last pushed 2d ago), licensed MIT. It adds 428 tokens to every session and 3,611 once invoked, about $0.0021 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.

Related

Other skills, from other repositories

i18n-localization

Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.

vudovn/ag-kit · 27 tokens

seedance-vocab-ja

This skill should be used when the user asks for Japanese Seedance 2.0 prompt wording, Japanese cinematic vocabulary, or translation of camera, lighting, action, VFX, audio, and production terms into Japanese.

Emily2040/seedance-2.0 · 50 tokens

asc-subscription-localization

Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.

rorkai/app-store-connect-cli-skills · 60 tokens

harden

Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready.

childrentime/reactuse · 32 tokens

subtitle-translator

Translate subtitle files (SRT, ASS) and video/media with embedded subtitles into any target language with high linguistic quality, sliding context window, timestamp alignment, and formatting preservation. Use when the user asks to translate a subtitle file (.srt, .ass) or video subtitles.

MaKTaiL/gemini-srt-translator · 60 tokens

iflytek-text-proofread

Proofread Chinese text using iFlytek's Official Document Proofreading API (公文校对). Detects 27 types of errors across three categories.

iflytek/iFly-Skills · 88 tokens