claudeers.
// Developer Tools

plus62

+62 Mode & Anti-Yapping Layer for Coding Agents. Langsung to-the-point ke baris bug, zero basa-basi korporat, dan anti-reasoning dump. (Claude Code, Antigrav…

// Developer Tools[ cli ][ api ][ desktop ][ mobile ][ claude ]#claude#antigravity#claude-code#coding-agent#cursor#indonesia#llm#opencode#devtools◷ MIT$open-sourceupdated 8 days ago

Install with your AI

Paste into Claude Code, Cursor, or any agent — it reads the repo and wires the tool into your project.

Install and set up plus62 (npm project) into my current project.
Found on https://claudeers.com/plus62
Repo: https://github.com/humanoiseLABS/plus62
Homepage/docs: https://hahahah-web.vercel.app
Detected install method: npm → npm install @humanoiselabs/plus62
Category: devtools. Platforms: cli, api, desktop, mobile.
Read the repo's README for exact setup and env vars, then install it and wire it into my project.

Claudeers Health Verdict:
unknown; community-verified: false. Confirm the source before running anything.
// or install directly (npm)
npm install @humanoiselabs/plus62
// or clone
git clone https://github.com/humanoiseLABS/plus62

// compatibility

Platformscli, api, desktop, mobile
Operating systems—
AI compatibilityclaude
LicenseMIT
Pricingopen-source
LanguageTypeScript

Get your FREE $2.50 API credits to access TickAtlas financial data ↗

🇮🇩 +62 Mode (plus62)

HumanoiseLABS (@humanoiseLABS) builds zero-fluff instruction & guardrail layers for AI coding agents across two flagship products:

ProductPackage / RepoFocusInstall Command
+62 Mode (this repo)plus62 (humanoiseLABS/plus62)Partner Ngoding Lokal (+62 Bloko Suto) — Bahasa Indonesia developer persona (lu/gw), zero corporate preamble, suppresses leaked reasoning dumps, cultural lexicon, & Risk Class 0–4 safety guardrails. Binaries: plus62, 62-mode, hahahah-ai, hahahah.npx plus62 install
Token-Maxxing (companion product)token-maxxing (humanoiseLABS/token-maxxing)Second Brain & Surgical Diffs — Stop yapping, start token-maxxing. Second Brain memory, surgical AST diffs, and real-time 3D neural telemetry HUD. Binaries: token-maxxing, tmx.npx token-maxxing install (or tmx)

(Note: Internally in this repository, +62 Mode uses the canonical profile ID plus62 (with backward-compatible alias rusuh-id), which is enabled by default so you never need to pass --profile manually. Qoder is still an incomplete compatibility assessment and makes no compatibility claim.)

Quick Install (via NPM / NPX — Tanpa Perlu Clone Repo)

Paket resmi +62 Mode tersedia di npm sebagai plus62 (dengan alias 62-mode, hahahah-ai, hahahah). Buka terminal di folder project kodingan lu, lalu jalankan:

# Claude Code (default)
npx plus62 install --target .

# Google Antigravity (global untuk semua project)
npx plus62 install --adapter antigravity --target ~/.gemini --scope global

# OpenCode
npx plus62 install --adapter opencode --target .

# Cursor / Codex / Windsurf (AGENTS.md)
npx plus62 install --adapter agents-md --target .

# Qoder (global untuk semua project & sesi lama/baru, atau per-project)
npx plus62 install --adapter qoder --scope global
npx plus62 install --adapter qoder --target .

# GitHub Copilot
npx plus62 install --adapter copilot --target .

# Cek integritas, update, atau uninstall kapan saja:
npx plus62 doctor --target .
npx plus62 update --target .
npx plus62 uninstall --target .

(Opsional) Jika ingin menginstal CLI secara global agar bisa langsung memanggil plus62 / 62-mode:

npm install -g plus62
plus62 install --target .

🤖 AI Self-Install Instructions (Jika User Menyuruh AI Memasang via Prompt / Repo / ZIP)

PERHATIAN UNTUK AI AGENT (Claude Code, Qoder, Antigravity, OpenCode, Cursor, Windsurf, Copilot): Jika user menyuruhmu memasang +62 Mode / plus62 ("pasang ini", "install +62 Mode", dll.), JANGAN hanya merangkumnya ke memori sopan dan JANGAN menginstal dengan --target . di dalam folder source plus62 itu sendiri! Ikuti langkah wajib berikut:

  1. Gunakan npx -y plus62 langsung di <TARGET_PROJECT> milik user (atau jika sedang berada di dalam clone repo plus62, jalankan npm ci lalu gunakan node src/cli.ts):
    • Claude Code:
      • Per-project: npx -y plus62 install --adapter claude-code --target <TARGET_PROJECT>
      • Global (agar aktif di semua project): jalankan juga dengan --target ~/.claude
    • Google Antigravity:
      • Global (semua project): npx -y plus62 install --adapter antigravity --target ~/.gemini --scope global
      • Per-project: npx -y plus62 install --adapter antigravity --target <TARGET_PROJECT>
    • Qoder (IDE / CLI / General Chat):
      • Jalankan: npx -y plus62 install --adapter qoder --target <TARGET_PROJECT>
      • WAJIB UNTUK QODER: Karena Qoder Desktop / General Chat sering tidak me-load .qoder/skills/hahahah-plus62/SKILL.md secara otomatis saat menerima sapaan kasual singkat (mis. "woy anjing"), baca penuh file .qoder/skills/hahahah-plus62/SKILL.md (atau personas/plus62/voice.md) lalu gabungkan (append) seluruh aturan suaranya langsung ke dalam AGENTS.md di <TARGET_PROJECT> serta simpan aturan lengkap tersebut (termasuk bagian Reflexes, Adaptive dynamics, dan Target) ke dalam Global Rules / Memory Qoder milikmu tanpa diperhalus!
    • OpenCode: npx -y plus62 install --adapter opencode --target <TARGET_PROJECT>
    • Cursor / Codex / Windsurf / Agent lain: npx -y plus62 install --adapter agents-md --target <TARGET_PROJECT> (dan salin isi .agents/skills/hahahah-plus62/SKILL.md langsung ke AGENTS.md / .cursorrules / .windsurfrules jika skill on-demand tidak otomatis aktif).
  2. Verifikasi & Aktifkan Persona Seketika:
    • Jalankan npx -y plus62 doctor --target <TARGET_PROJECT>
    • Baca penuh CLAUDE.md / AGENTS.md dan file SKILL.md yang baru terpasang sekarang juga.
    • Langsung balas user menggunakan gaya +62 Mode (lu/gw, blak-blakan, reaksi kapital WKWKWK, variasi emot 😂 😹 🖕 🤓 😭 sesuai konteks, DILARANG spam 💀, sikat balik kalau dipancing ngomong kasar, HARAM menjawab sopan ala bot korporat seperti "Ada yang bisa dibantu? Santai dong").

Commands

Install: pick the adapter for the agent you actually run

--adapter decides which files land where. Pick it from the agent, not from the folder — installing for the wrong one writes files that agent never reads, and the persona silently does nothing.

Agent you runCommandWhat it writes
Claude Code (default)npx plus62 install --target <project>CLAUDE.md block + .claude/skills/hahahah-plus62/
opencodenpx plus62 install --adapter opencode --target <project>AGENTS.md block + .claude/skills/ (opencode reads that tree)
Antigravity, one projectnpx plus62 install --adapter antigravity --target <project>AGENTS.md block + .agents/rules/*.md
Antigravity, every projectnpx plus62 install --adapter antigravity --target ~/.gemini --scope globalAGENTS.md block + config/rules/*.md
Cursor / Codex / anything reading AGENTS.mdnpx plus62 install --adapter agents-md --target <project>AGENTS.md block + .agents/skills/
Qoder CLInpx plus62 install --adapter qoder --target <project>AGENTS.md block + .qoder/skills/
GitHub Copilotnpx plus62 install --adapter copilot --target <project>.github/copilot-instructions.md, voice folded in — it documents no on-demand layer

node src/cli.ts with no arguments prints this same table. Uninstall needs only --target: the manifest remembers the adapter, the scope, and every path it wrote.

How far each of those claims actually goes

Two different things get confused easily, so they are recorded separately: what the vendor documents, and what anyone has observed on real hardware. test/adapter-coverage.test.ts fails CI if an adapter is registered without a row here, if the emitted paths or required frontmatter drift from the documented ones, or if this table stops matching the registry.

AdapterAlways-on fileOn-demand layerVerification statusSource of the expectation
claude-codeCLAUDE.md.claude/skills/…/SKILL.mdverified on this machinehttps://code.claude.com/docs/en/skills
opencodeAGENTS.md.claude/skills/…/SKILL.mdverified on this machineopencode 1.18.31 debug skill listed the installed skill locally
agents-mdAGENTS.md.agents/skills/…/SKILL.mddocumented, not verifiedhttps://agentskills.io/specification
antigravityAGENTS.md.agents/rules/*.mddocumented, not verifiedhttps://antigravity.google/docs/rules/
qoderAGENTS.md.qoder/skills/…/SKILL.mddocumented, not verifiedhttps://docs.qoder.com/cli/Skills
copilot.github/copilot-instructions.mdnone — the voice is folded into the filedocumented, not verifiedhttps://docs.github.com/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot

"Documented, not verified" means the files are exactly where the vendor says the agent will look, and the install round-trips — but no Cursor, Codex, Qoder or Antigravity run on this machine has yet been shown reading them. Do not present those rows as tested compatibility.

copilot is the one row that costs real tokens every turn. GitHub documents no on-demand layer for the coding agent, so the full voice has to live inside the instructions file: measured 2342 tokens of always-on content against 462 for the card-only layouts. The build says so in its warnings rather than letting the global card-sized budget hide it. Copilot is also the reason it is not the reference target — personal instructions outrank repository instructions, so a safety-sensitive layer cannot rely on being the last word.

npm ci
npm run typecheck
npm test
npm run measure
node src/cli.ts measure --profile plus62 --adapter claude-code
node src/cli.ts install --profile plus62 --target /path/to/project --dry-run
node src/cli.ts install --profile plus62 --target /path/to/project
node src/cli.ts update --target /path/to/project
node src/cli.ts doctor --target /path/to/project
node src/cli.ts eval --profile plus62 --suite smoke --limit 1 --budget-usd 0.10
node src/cli.ts eval --profile plus62 --suite safety --task saf-religion-fatwa-01 --budget-usd 0.20 --strict
node src/cli.ts eval --profile plus62 --suite decisions --limit 4 --budget-usd 0.20
node src/cli.ts uninstall --target /path/to/project
  • measure prints token budgets without writing.
  • install writes the managed block, the adapter's skill or rules tree, and .plus62/manifest.json (with backward-compatible support for legacy .hahahah/manifest.json).
  • update refreshes the managed block and skill tree to the latest canonical version using the target manifest.
  • doctor verifies files, hashes, and the managed block.
  • uninstall removes only manifest-owned content.
  • eval runs baseline/treatment headless; --harness claude|opencode picks the CLI and the adapter the treatment is installed for, since a mismatch measures nothing. --task <id> selects tasks; --strict exits non-zero when a treatment answer fails a screen.
  • build with the fake adapter remains available for deterministic contract tests.

Current status

  • Core policies: authored and within the always-on target (Claude managed block 420/420; hard cap 600). The full identity/safety/decision/efficiency policy text ships as on-demand skill references, so a reviewed rule can no longer be unreachable at runtime. Human review pending.
  • Phase 3 content fixes: the always-on core carries a language policy, an explicit no-religious-ruling rule, and A user can waive scope, not truth. — each driven by an observed live failure. See docs/phase-3-content-hardening.md.
  • Eval: deterministic language/require/forbid screens (src/checks.ts). These are surface screens for triage, not semantic judges. Every campaign is guarded against the ways the numbers used to lie: one cheap route probe runs before the paid loop (a stopped gateway used to look like a slow campaign, and burned 13 runs that way), runs that never answered are counted in errored and kept out of every median, and routing flags runs whose prompt size sits outside 0.6x-1.6x of the campaign median because a gateway that picks an upstream per request changes the model underneath an A/B — measured on this machine: 4 of 72 runs came back from a different upstream, at 63,578 input tokens against a 19,328 median. Prompt size means the whole input side, cache reads included: opencode reports only the uncached remainder in tokens.input, so one 6,308-token prompt came back as 4,453 cold and 36 warm, and reading input alone published a false route-split warning over 17 of 35 runs before promptTokens() existed. The provider base URL is read from the harness's own settings file (host and port only, never the credential beside it) so report.md can name the route a campaign ran against. A gateway that refuses on request quota aborts the campaign at the first refusal and writes a partial report naming the tasks it never reached, rather than spending the remaining runs on one identical error (12 were lost that way before this existed). Three consecutive runs answered with nothing at all abort on the same terms, because a route that times out at the spawn limit will do it 72 times (11 runs and 33 minutes before this was named) — but that label reports what reached the process, not the cause: opencode logs Free usage limit reached under a second into a call and then hangs instead of exiting, so two campaigns were labelled unresponsive while the free tier was refusing — report.md now says to read the harness's own log before naming a cause, and the opencode runner reads it for you, matching the workspace it just ran so a refusal that never reaches stdout still aborts the campaign at the first run instead of the third. Each report also fingerprints its own prompts and screens (tasksSha256, hahahah.eval/v7), because editing a screen silently changes what every pass rate in the suite means.
  • Suites: evals/smoke.yaml (5), evals/decisions.yaml (24), evals/safety.yaml (24), evals/preservation.yaml (12), evals/rusuh-voice.yaml (17) — 82 tasks, all listed by --help, all carrying language plus require/forbid screens, coverage of every documented instruction class, risk class 0–4, and safety threat family asserted by test, and screen patterns compiled at suite load so a broken regex fails before any API call. Five tasks in rusuh-voice carry turns instead of a single prompt: every turn is sent in order with the transcript so far, each turn's own screens judge that turn, and a cross-turn repeat check fails when the next answer reuses a four-word run from the previous one. The transcript is replayed text, not a resumed harness session — runClaude spawns with --no-session-persistence — so a multi-turn report must say which it is. The 25-case personas/*/tests.yaml rubrics are labelled manual-rubric: nothing executes them, and rusuh-voice is the measured counterpart.
  • Live results on the current provider (64 tasks across four suites, ≈$22.1): the language policy holds across models — baseline answered English on 29 of 47 tasks in the first two suites, the treatment on 4; the 5 newest injection vectors were refused cleanly 5/5. The layer's real input cost is +710 tokens/run (ablation: 19,048 → 19,758); the apparent +95% cost was the gateway rotating a combo of four upstream models per request (the same brief came back with prompt sizes from 6k to 62k tokens), not the persona, which is why the runner now reports medians over k repeats. Open behaviour findings: a payment-path caution dropped under a length constraint, and one reply came back with unfilled [placeholders]. See docs/phase-3-live-suite-results.md.
  • Clean measurement of the efficiency question (docs/evidence/efficiency-clean/findings.md): preservation suite, k=3, upstream pinned with --model kr/claude-sonnet-4.5-agentic, the gateway's Caveman and Ponytail layers confirmed off before launch. 60 of 72 runs answered — 12 lost to the free connection's request quota, recorded as errored and excluded from every median. The layer costs +738.5 input tokens/request and about 1% more per run, and does not shorten answers: reply substance is +21.9% longer, 7 of 10 tasks. What it changes is delivery and discipline: the plain prompt emits its reasoning block inside the reply in 16 of 30 runs against 3 of 30 with the persona, so the text a user scrolls is 51.2% shorter; Indonesian in the answer rises from 19/30 to 27/30 and screens from 58 to 67 passing of 75, while require retention is identical at 34/39 in both arms — the longer substance is not buying completeness. Per task the treatment is better on 5 of the 10 answered tasks, equal on 3 and worse on 2 (pres-constraint-01, pres-security-note-01), which is the honest shape of it. There is no measured output compression in this project; a "write less code" rule would be the first attempt at it, and this run is the baseline to measure it against. Two ruler defects were found in this campaign and fixed: screens were satisfied by text that appeared only inside a reasoning dump, and one reported "regression" turned out to be the screen, not the persona (pres-honest-partial-01 now passes 3/3 in both arms). Reports now fingerprint the prompts and screens that produced them (tasksSha256, hahahah.eval/v5) so a ruler edit cannot silently make two campaigns incomparable.
  • Second-harness replication (docs/evidence/efficiency-opencode/findings.md): the same suite on opencode 1.18.31 with --model opencode/beam-free, k=3, both gateway style layers off, $0.0000. The free tier started refusing after 35 answered runs and the breaker stopped the campaign at 38, so 6 of 12 tasks are measured; a later attempt to measure the rest died at the route probe on the same refusal, and the report's unresponsive label was wrong — opencode logged Free usage limit reached in under a second and then hung, which surfaced as a 180 s spawn timeout. The overhead claim survives: +646.5 input tokens (difference of arm medians) / +647 (median of paired per-task deltas, range +645…+651), which is +10.25% on opencode's ~6,305-token base prompt against ~2.3% on Claude Code's ~30.9k — the absolute cost is the layer's fixed text, the relative cost belongs to the host. Two headline effects do not replicate and must be quoted with the kiro route attached: neither arm emitted a reasoning dump here (0/18 and 0/17, against 16/30 and 3/30 there), so the "51.2% less scrolling" disappears, and reply substance moves −2 characters (median paired delta, 2 tasks longer / 4 shorter) instead of +21.9%. Behaviour is worse on this route, not better: screens 33 pass / 7 fail against the baseline's 37 / 4, and require retention 21/23 against 24/24 — one repeat of pres-warning-kept-01 dropped the deprecation and token-format warnings the baseline kept.
  • Coding fixtures: fixtures/ holds the full set of 60 planned micro-tasks (10 marked hidden holdout), each a broken file plus a real node --test suite and a reference solution. node src/cli.ts fixtures check proves every fixture is red before the fix and green after it, and runs in CI — it already caught one fixture whose own test assertion was wrong. The runner only accepts node --test: no shell, no inherited NODE_OPTIONS, no option or traversal in the target. node src/cli.ts fixtures run is the model-facing half: it seeds the same broken files into a bare and an installed repository, sends both arms the identical brief, then grades each workspace by executing the fixture's own tests — so a solved here is a fix that works, not an answer that reads well. Editing, deleting, or adding a test file is graded tampered and never counted as solved; a run that did not complete is error and is not scored. Spend is opt-in: without --live nothing is called, and with --live the command refuses until --max-total-usd states the approved ceiling. Two independent review rounds then closed seven briefs that under-stated a rule their own test enforced, loosened two assertions that pinned style instead of behaviour, and pinned the grading environment after measurement showed a host could move a grade — declared test files only, process.execPath, TZ=UTC, seeded module manifest (TECHNICAL_RISKS.md R-35, docs/phase-3-live-suite-results.md §11). The preflight is answered, and the culprit was ours: os.tmpdir() on this machine returns a Windows 8.3 short path, the harness then required approval for every tool inside it (even Glob), and three paid runs read nothing at all. With the temp root resolved through realpathSync.native, a live arm read the tests, found the boundary bug on its own, and wrote the fix: acceptEdits really does grant Read/Glob/Edit headless, and Bash is refused exactly as designed. Still open: a per-run budget big enough for a run to finish (≈$1-1.5 per arm measured, so a 60-fixture k=1 pass is $120-180 — see docs/phase-3-live-suite-results.md §15), and a reviewer reading each brief against its reference solution — the validator proves a fixture is solvable and gradeable, not that the reference solution is the only defensible reading.
  • Licence: MIT (LICENSE), chosen 2026-11-07 over Apache-2.0 because this repository is policy text and a small TypeScript compiler with nothing patentable, and MIT adds no NOTICE or change-marking step for the harnesses that will bundle it.
  • Provenance: verified KBBI and NU Online citations for the religious expressions live in culture/id/sources.md, which is deliberately not mounted — references cost runtime tokens, citations do not. MasyaAllah and Subhanallah still have no verified URL, and inventing a decay_class for religious vocabulary was rejected as a distortion rather than a fix.
  • Personas: +62 Mode (profiles/plus62.yaml, alias: rusuh-id) is authored with voice, card, lexicon, examples, and rubric scenarios. +62 Mode (plus62) is signed off across all three review axes (linguistic, cultural, safety) and passes build --release. Installs and uninstalls cleanly across all supported harness adapters.
  • Culture KB: small sourced seed. culture/id/religious-expression.md and the four expanded core/*.md policies are mounted as skill references.
  • Harnesses: Claude Code is the reference target and is verified end-to-end (install, doctor, uninstall, live run, permission posture measured). opencode (1.18.31) has its own adapter plus a headless runner (--harness opencode): opencode debug skill lists the installed skill, a live opencode run confirmed the AGENTS.md block reaches model context, and a coding fixture graded solved with the edit landing in the graded workspace — see docs/harness-parity.md. Its study posture is enforced through OPENCODE_CONFIG (edit allow, bash/webfetch/external_directory deny) rather than by writing into the target repo. antigravity has an adapter that writes .agents/rules/*.md with always_on/model_decision triggers, plus --scope global for ~/.gemini/config/rules/; that layout follows the vendor docs and has not been observed loading. agents-md emits the vendor-neutral AGENTS.md + .agents/skills/ pair; it is exercised by install/doctor/uninstall round-trips but no Cursor/Codex/Qoder run has read it on this machine. Qoder itself remains unverified — docs/qoder-assessment.md still says "Incomplete — no compatibility claim".

See docs/quickstart.md, docs/phase-2-integration-findings.md, docs/phase-3-content-hardening.md, docs/phase-3-live-suite-results.md, and the Phase 0 documents.

// faq

What is plus62?

+62 Mode & Anti-Yapping Layer for Coding Agents. Langsung to-the-point ke baris bug, zero basa-basi korporat, dan anti-reasoning dump. (Claude Code, Antigravity, OpenCode, Qoder, Codex, Hermes, Cursor). It is open-source on GitHub.

Is plus62 free to use?

plus62 is open-source under the MIT license, so it is free to use.

What category does plus62 belong to?

plus62 is listed under devtools in the Claudeers registry of Claude-compatible tools.

2 views
★ 10 stars
unclaimed
updated 8 days ago

// embed badge

plus62 on Claudeers
[![Claudeers](https://claudeers.com/api/badge/plus62.svg)](https://claudeers.com/plus62)

// retro hit counter

plus62 hit counter
[![Hits](https://claudeers.com/api/counter/plus62.svg)](https://claudeers.com/plus62)

// reviews

// guestbook

0/500

// related in Developer Tools

🔓

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Curs…

// devtoolsaffaan-m/⟨JavaScript⟩★ 297,269◷ MIT[ claude ]
🔓

Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.

// devtoolsDietrichGebert/⟨JavaScript⟩★ 187,728◷ MIT[ claude ]
🔓

AI coding assistant skill (Claude Code, Codex, OpenCode, Cursor, Gemini CLI, and more). Turn any folder of code, SQL schemas, R scripts, shell scripts, docs,…

// devtoolssafishamsi/⟨Python⟩★ 147,800◷ MIT[ claude ]
🔓

Use Garry Tan's exact Claude Code setup: 23 opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA

// devtoolsgarrytan/⟨TypeScript⟩★ 140,465◷ MIT[ claude ]
→ see how plus62 connects across the ecosystem