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 6529-Collections/6529seize-frontend --skill 6529-agent-logingit clone --depth 1 https://github.com/6529-Collections/6529seize-frontendWrote 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/6529-collections/6529seize-frontend/6529-agent-login)<a href="https://agentmods.dev/skills/6529-collections/6529seize-frontend/6529-agent-login"><img src="https://agentmods.dev/badge/skills/6529-collections/6529seize-frontend/6529-agent-login/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/6529-collections/6529seize-frontend/6529-agent-login"><img src="https://agentmods.dev/badge/skills/6529-collections/6529seize-frontend/6529-agent-login.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 18 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 144 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00079 | $0.01721 |
| Opus 5 | $0.00039 | $0.00860 |
| Sonnet 5 | $0.00016 | $0.00344 |
| Haiku 4.5 | $0.00008 | $0.00172 |
Grade A, and why
6529-agent-login 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 11d 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
6529 Agent Login
Overview
Use this skill to log browser agents into a local 6529 frontend without adding
wallet code to the app. The helper script keeps test wallet keys outside the
repo by default, performs the normal session-v2 API login, and emits either a
Playwright storage-state file, browser JavaScript, or a JSON payload for the
development-only /tools/agent-login bridge route.
Do not use this for production accounts unless the user explicitly provides a dedicated test key. Do not commit account pool files, private keys, emitted JSON payloads, storage-state files, cookies, access tokens, or generated login scripts.
If the configured API endpoint is production and the QA task will create profiles, direct messages, drops, or other persistent data, get explicit user confirmation before performing those browser actions.
Helper
From the repository root, use:
node ops/skills/6529-agent-login/scripts/agent-login.mjs <command>
The helper defaults to:
- account pool:
~/.codex/6529-agent-login/accounts.json - repo env source: current working directory, or
--repo /path/to/6529seize-frontend - API endpoint:
API_ENDPOINTfrom repo.env, or--api https://... - local browser origin for storage-state output:
BASE_ENDPOINT, orhttp://localhost:3001
The helper resolves ethers from the repo's node_modules; pass --repo when
running outside the frontend repo.
Use --state /path/to/accounts.json only for a developer-local account pool.
Never point --state at a tracked file.
Account Pool
Use accounts.example.json as a shape reference only. Do not fill that file, or
any other tracked file under ops/, with real private keys.
List accounts:
node ops/skills/6529-agent-login/scripts/agent-login.mjs list
Create a throwaway wallet:
node ops/skills/6529-agent-login/scripts/agent-login.mjs create --id agent-a --label "Agent A"
Import a seeded test account:
node ops/skills/6529-agent-login/scripts/agent-login.mjs import --id seeded-a --private-key 0x...
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 228 lines · 79 tokens per session scan A f60295030699
6529-agent-login is a skill published in the GitHub repository 6529-Collections/6529seize-frontend (10 stars, last pushed today), licensed Apache-2.0. It adds 79 tokens to every session and 1,721 once invoked, about $0.0004 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
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…