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 Bynn-Intelligence/skills --skill bynn-web-sdkgit clone --depth 1 https://github.com/Bynn-Intelligence/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/bynn-intelligence/skills/bynn-web-sdk)<a href="https://agentmods.dev/skills/bynn-intelligence/skills/bynn-web-sdk"><img src="https://agentmods.dev/badge/skills/bynn-intelligence/skills/bynn-web-sdk/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/bynn-intelligence/skills/bynn-web-sdk"><img src="https://agentmods.dev/badge/skills/bynn-intelligence/skills/bynn-web-sdk.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.00089 | $0.02188 |
| Opus 5.5 | $0.00036 | $0.00875 |
| Sonnet 5.5 | $0.00018 | $0.00438 |
| Haiku 4.5 | $0.00009 | $0.00219 |
Grade A, and why
bynn-web-sdk scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://registry.npmjs.org/@bynn-intelligence/websdk/latest | jq -r .version How it starts
The opening of the file, as written. The whole thing — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bynn Web SDK
The fastest way to put identity verification on a page. The SDK renders the form, creates the session, and opens the verification flow. You provide a public key, a KYC level, and a parent element.
Install
Package manager, which is the path that stays current on its own:
npm install @bynn-intelligence/websdk
import { Bynn } from '@bynn-intelligence/websdk';
Script tag, from a CDN that resolves to the latest published build:
<script src="https://unpkg.com/@bynn-intelligence/websdk/dist/bynn.min.js"></script>
<script type="module">
import * as Bynn from 'https://unpkg.com/@bynn-intelligence/websdk/dist/bynn.esm.js';
</script>
https://cdn.jsdelivr.net/npm/@bynn-intelligence/websdk/dist/bynn.min.js works the same
way if you prefer jsDelivr.
Pinning a version
Pinning is the right call for production, because an unversioned CDN URL means a third party can change your verification flow without a deploy on your side. Bynn serves version-pinned builds at:
https://static.bynn.com/sdk/js/<version>/bynn.min.js
https://static.bynn.com/sdk/js/<version>/bynn.esm.js
Look the current version up rather than copying one. Any of these answers it:
npm view @bynn-intelligence/websdk version
curl -s https://registry.npmjs.org/@bynn-intelligence/websdk/latest | jq -r .version
The dashboard also shows a ready-made snippet with the current version at
https://dashboard.bynn.com/integration, under "Bynn.js (easy integration)".
Then pin deliberately and upgrade on your own schedule. A version number written down in a guide is stale the moment a release ships, so treat any version you see quoted anywhere as an example, not as the current one.
Mount
The SDK needs one parent element:
<div id="verification-form"></div>
const bynn = Bynn({
apiKey: 'your_PUBLIC_api_key',
kycLevel: 'your_kyc_level',
parentId: 'verification-form',
fields: [
{ name: 'first_name', visible: true },
{ name: 'last_name', visible: true },
{ name: 'email_address', visible: false, value: '[email protected]' },
{ name: 'phone_number', visible: true },
{ name: 'unique_id', visible: false, value: '550e8400-e29b-41d4-a716-446655440000' }
]
});
bynn.mount();
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.
- 4d ago Changed 2d14ae80fbec
- 1mo ago First seen · 253 lines · 89 tokens per session scan A c2eb2d6654fa
bynn-web-sdk is a skill published in the GitHub repository Bynn-Intelligence/skills (0 stars, last pushed 4d ago), licensed MIT. It adds 89 tokens to every session and 2,188 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
compliance-documentation-requirements
Use when setting up or auditing how compliance documentation is structured, collected, and preserved for regulatory audit in Salesforce FSC — covering KYC data collection workflows, AML screening integration setup, audit trail configuration, and regulatory reporting readiness. Triggers: KYC form setup, AML integration…
compliance-documentation-requirements
Use when setting up or auditing how compliance documentation is structured, collected, and preserved for regulatory audit in Salesforce FSC — covering KYC data collection workflows, AML screening integration setup, audit trail configuration, and regulatory reporting readiness. Triggers: KYC form setup, AML integration…
fto-triage
Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent…
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
terms-of-service
Draft terms of service and a companion privacy notice matched to the product's form and feature modules, not legal advice, delivered as a Word document.