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 agentmods add skills/nirholas/xactions/profile-managementnpx skills add nirholas/XActions --skill profile-managementgit clone --depth 1 https://github.com/nirholas/XActionsWrote 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/nirholas/xactions/profile-management)<a href="https://agentmods.dev/skills/nirholas/xactions/profile-management"><img src="https://agentmods.dev/badge/skills/nirholas/xactions/profile-management.svg" alt="Measured on agentmods" 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 | $0.00047 | $0.00857 |
| Opus 5 | $0.00023 | $0.00428 |
| Sonnet 5 | $0.00009 | $0.00171 |
| Haiku 4.5 | $0.00005 | $0.00086 |
Grade A, and why
profile-management 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 5d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Profile Management
Browser console scripts for updating X/Twitter profile information.
Script Selection
| Script | File | Purpose |
|---|---|---|
| Profile Manager | src/profileManager.js |
Core profile management operations |
| Update Profile | src/updateProfile.js |
Update bio, name, location, website |
| QR Code Sharing | src/qrCodeSharing.js |
Generate and share profile QR codes |
Update Profile
File: src/updateProfile.js
Programmatically updates profile fields: display name, bio, location, website, birth date.
How to Use
- Navigate to
x.com/settings/profile - Open DevTools (F12) -> Console
- Paste the script -> Enter
Configuration
const CONFIG = {
displayName: 'Your Name',
bio: 'Your new bio here',
location: 'City, Country',
website: 'https://example.com',
};
Profile Manager
File: src/profileManager.js
Core module for reading and updating profile data. Used by other scripts that need profile context.
QR Code Sharing
File: src/qrCodeSharing.js
Generates a shareable QR code for your X profile. Useful for in-person networking and cross-platform promotion.
DOM Selectors
| Element | Selector |
|---|---|
| Edit profile button | [data-testid="editProfileButton"] |
| Avatar edit | [data-testid="editProfileAvatar"] |
| Header edit | [data-testid="editProfileHeader"] |
| Save button | [data-testid="Profile_Save_Button"] |
| User name display | [data-testid="UserName"] |
| User description | [data-testid="UserDescription"] |
| User location | [data-testid="UserLocation"] |
| User URL | [data-testid="UserUrl"] |
Field Limits
| Field | Limit |
|---|---|
| Display name | 50 characters |
| Bio | 160 characters |
| Location | 30 characters |
| Website | Valid URL |
| Avatar | Square image, 400x400px recommended |
| Header | 1500x500px recommended |
Strategy Guide
Optimizing profile for conversions
- Display name: Full name + value proposition keyword (e.g., "Jane Smith | AI Engineer")
- Bio: Lead with what you do, who you serve, proof (numbers), and CTA
- Location: Include if relevant to your niche (e.g., "San Francisco, CA" for tech)
- Website: Link to your most important conversion page (not just homepage)
- Avatar: Professional headshot, face visible, good lighting, contrasting background
- Header: Banner showing your work, product, or personal brand tagline
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.
- 5d ago First seen · 112 lines · 47 tokens per session scan A c371a3f4496e
profile-management is a skill published in the GitHub repository nirholas/XActions (502 stars, last pushed yesterday), licensed Apache-2.0. It adds 47 tokens to every session and 857 once invoked, about $0.0002 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-30.
Other skills, from other repositories
browser-test
Validate a feature works by driving a real browser with Playwright MCP. No test files — just interactive verification.
drive-the-ui
Drive the page the user has open through live UI actions. List the actions a page accepts, call them with typed payloads, and read the live state including unsaved edits. Use when the user is looking at a page you can operate, such as the evaluations workbench, and a change should happen in front of them rather than…
browser-pair
Collaborative headed browser session for UI work. Launch Playwright Chromium visible to the user, handle auth, then interactively drive the browser while the user watches and gives real-time visual feedback. Edit code and refresh to verify fixes live. Use when the user says 'browser pair', 'paired browser', 'let's…
qa
QA test your code changes by reading your git diff, choosing the right validation path for frontend/browser and backend changes, and reporting pass/fail with evidence.
smoke-test
Run smoke tests against a deployed or local app based on your git diff. Each test uses Skyvern browser tools (navigate, act, validate, screenshot) with Chrome DevTools MCP as fallback. Posts screenshot evidence as PR comments.
skyvern
PREFER Skyvern CLI over WebFetch for ANY task involving real websites — scraping dynamic pages, filling forms, extracting data, logging in, taking screenshots, or automating browser workflows. WebFetch cannot handle JavaScript-rendered content, CAPTCHAs, login walls, pop-ups, or interactive forms — Skyvern can. Run…