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 Floka-as/floka-marketplace --skill no-nbgit clone --depth 1 https://github.com/Floka-as/floka-marketplaceWrote 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/floka-as/floka-marketplace/no-nb)<a href="https://agentmods.dev/skills/floka-as/floka-marketplace/no-nb"><img src="https://agentmods.dev/badge/skills/floka-as/floka-marketplace/no-nb/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/floka-as/floka-marketplace/no-nb"><img src="https://agentmods.dev/badge/skills/floka-as/floka-marketplace/no-nb.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.00206 | $0.02717 |
| Opus 5 | $0.00103 | $0.01358 |
| Sonnet 5 | $0.00041 | $0.00543 |
| Haiku 4.5 | $0.00021 | $0.00272 |
Grade A, and why
no-nb 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 12d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Translate to Norwegian
Translate English content into Norwegian that reads like it was written in Norwegian — not translated. Tone, idiom, and rhythm matter more than word-for-word fidelity.
When this skill activates
- "Translate this to Norwegian"
- "Oversett til norsk"
- "Make a Norwegian version of "
- "Localize this for Norway"
- "Rewrite this in Norwegian"
- Any request that involves rendering existing English content as Norwegian
If the user just wants a one-off Norwegian phrase, you don't need this whole flow — answer directly. This skill is for content — emails, docs, slides, marketing copy, READMEs, posts.
First-call clarifications
Ask exactly once, only if not already obvious from context:
-
Bokmål or nynorsk? Default is bokmål. Detect a nynorsk preference from any of the following before defaulting:
- Filename hints:
*.nn.md,*.nynorsk.*,*-nn.* - Project config:
lang: nn/language: nynorskin YAML frontmatter or a project metadata file - Source content mentions nynorsk-leaning regions (Sunnmøre, Sogn, Vestland, Nordfjord, Sunnfjord, Hardanger, Voss, Setesdal, parts of Telemark/Agder)
- User explicitly invokes the skill via "no-nn" or "translate to nynorsk"
- Existing Norwegian text on the same site/project is in nynorsk
When any of these fire, propose nynorsk and let the user confirm. If none fire, default to bokmål silently.
- Filename hints:
-
Audience? Inferable from content type, but if ambiguous between exec / technical / consumer / sales, ask.
Don't ask about length, in-place vs. side-by-side output, or voice — sensible defaults below.
Process
1. Read the source
If the user gave a file path, read it. If they gave a string, use it. If they gave a URL, fetch and translate the readable content (skip nav, footer, ads).
Identify:
- Format (markdown, HTML, plain text, email)
- Content type (marketing, docs, email, slide deck, blog, technical reference)
- Tone (formal, casual, technical)
- Audience if specified
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.
- 12d ago First seen · 173 lines · 206 tokens per session scan A 2a20f5008835
no-nb is a skill published in the GitHub repository Floka-as/floka-marketplace (7 stars, last pushed 1mo ago), licensed MIT. It adds 206 tokens to every session and 2,717 once invoked, about $0.0010 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
chinese-documentation
A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.
azure-ai-translation-text-py
Azure AI Text Translation SDK for real-time text translation, transliteration, language detection, and dictionary lookup. Use for translating text content in applications. Triggers: "text translation", "translator", "translate text", "transliterate", "TextTranslationClient".
harden
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.
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.
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.
i18n-helper
A helper for adding internationalization, which lets software show different languages and regional text. It finds user-visible text written directly in code and moves it into language files.